Re: t5559 breaks with apache 2.4.55

From: Jeff King <peff@peff.net>
Date: Jan 26, 2023, 11:39 UTC
Message-ID: <Y9Jmfg/jlSszVep4@coredump.intra.peff.net>
In-Reply-To: <Y81lQwG85+Skujja@pobox.com>

On Sun, Jan 22, 2023 at 11:33:07AM -0500, Todd Zullinger wrote:

Show 13 quoted lines

> > So I haven't reported the bug further yet. But I thought I'd post this
> > here before anybody else wastes time digging in the same hole.
> 
> FWIW, I think this is the same issue we discussed about 2
> months back, in <Y4fUntdlc1mqwad5@pobox.com>¹.
> 
> I haven't done much else with it since then.  It's almost
> surely either an apache httpd/mod_http2 or curl issue.  If I
> had to bet, I'd say mod_http2.  (But then, it could be curl
> and just has yet to be exposed widely because not many are
> using the current mod_http2 code.)
> 
> ¹ https://lore.kernel.org/git/Y4fUntdlc1mqwad5@pobox.com/

Ah, I somehow completely forgot about that issue. Despite being one of the two participants on the thread.

Yeah, after seeing that, I'm quite sure this is a mod_http2 issue. It would be nice to bisect within the mod_http2 history to find the culprit, but I'd first have to figure out how to build standalone apache modules. ;)

I may try to poke at it later if I have time. It might also be worth submitting a bug report to the mod_http2 folks. I'd hope to have a more compact reproduction, but it does at least seem to fail reliably for me (not even racily).

-Peff