From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 37EFA3858C2B; Fri, 16 Jun 2023 14:42:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 37EFA3858C2B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1686926548; bh=iGOMLB4/5nF1BH81gs2hPW97r6OKxM30mCL1toRk6RM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=p7hLKaGy7bq8MBwx1V2F4BK3vewdk0Sbj7ydwHf7mRvM7OKYCoBjok9SaZDEYhQpX +lq8vgiFj6fJn9KklQX/yrMWiKOMil/azLERlLQA7ue/9sjVv+6zsfEKYpU0UU96Pq XgLx7QE8h3S6wf/Avswty3pEs3rPoCymrJJG3fxU= From: "rgoldber at redhat dot com" To: elfutils-devel@sourceware.org Subject: [Bug debuginfod/29696] intermittent libmicrohttpd assertion failures related to socket fd closing Date: Fri, 16 Jun 2023 14:42:27 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: elfutils X-Bugzilla-Component: debuginfod X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rgoldber at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: rgoldber at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29696 --- Comment #3 from Ryan Goldberg --- I noticed that the issue was happening in run-debuginfod-federation-metrics= .sh so to reproduce I was playing with sending lots of requests to a federation= of servers. Only had the issue occur on the downstream so it was a client issu= e. This made it pretty quick to replicate, so I could go through debuginfod_query_server and see how far down I can put an early exit before seeing the race condition. That narrowed it down to debuginfod_config_cache. >From there noticed the double close and it was smooth sailing. I'm not sure about tooling around the double close but is it possible to kn= ow that something is a double close if the fd may just be reused? Since in this case for instance the close won't fail, we're just closing someone else's o= pen, good to go fd. fwiw I looked in elfutils at least and we didn't use fdopen = with a double close again. --=20 You are receiving this mail because: You are on the CC list for the bug.=