From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-3.8 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by dcvr.yhbt.net (Postfix) with ESMTP id 44D7F1F47C for ; Thu, 26 Jan 2023 11:40:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237307AbjAZLj6 (ORCPT ); Thu, 26 Jan 2023 06:39:58 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49718 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237288AbjAZLj4 (ORCPT ); Thu, 26 Jan 2023 06:39:56 -0500 Received: from cloud.peff.net (cloud.peff.net [104.130.231.41]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A17E663844 for ; Thu, 26 Jan 2023 03:39:43 -0800 (PST) Received: (qmail 20917 invoked by uid 109); 26 Jan 2023 11:39:43 -0000 Received: from Unknown (HELO peff.net) (10.0.1.2) by cloud.peff.net (qpsmtpd/0.94) with ESMTP; Thu, 26 Jan 2023 11:39:43 +0000 Authentication-Results: cloud.peff.net; auth=none Received: (qmail 22934 invoked by uid 111); 26 Jan 2023 11:39:42 -0000 Received: from coredump.intra.peff.net (HELO sigill.intra.peff.net) (10.0.0.2) by peff.net (qpsmtpd/0.94) with (TLS_AES_256_GCM_SHA384 encrypted) ESMTPS; Thu, 26 Jan 2023 06:39:42 -0500 Authentication-Results: peff.net; auth=none Date: Thu, 26 Jan 2023 06:39:42 -0500 From: Jeff King To: Todd Zullinger Cc: git@vger.kernel.org Subject: Re: t5559 breaks with apache 2.4.55 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Sun, Jan 22, 2023 at 11:33:07AM -0500, Todd Zullinger wrote: > > 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 ¹. > > 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