Apparently both bugs had been reported previously, pre-AI, if so some important questions need to be asked about how those reports slipped through without a fix.

▲

dwohnitmok 3 hours ago | parent | next [-]

I'm very confused about what's going on. In fact as far as I can tell those specific bugs were fixed.

https://bugs.php.net/bug.php?id=78876 marks the OOM bug as closed and fixed in 2020.

It seems the AI exploration was able to find variants of those bugs that were not fixed rather than exactly those bugs themselves?

	▲	amiga386 3 hours ago \| parent \| next [-]
		That report describes sending a 2^31 length filename, which is cast to a negative number, which leads to asking erealloc() to allocate a very large buffer, which fails, which leads to the symptoms of the bug we're discussing today (mid-request allocation failure becomes a partially initialised request) The fix at the time wasn't to do proper cleanup on eralloc() failure, it was merely to avoid filename length being cast to a negative number.
	▲	dspillett 3 hours ago \| parent \| prev [-]
		Or perhaps the fixes were not complete, and only addressed a specific test case instead of resolving the wider issue.

▲

thway15269037 3 hours ago | parent | prev [-]

"Looks minor, hard to reproduce, little affected area. Throw it into backlog for 2095 release cycle."