From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 92B63385840E; Wed, 15 Dec 2021 10:19:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 92B63385840E From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/28349] Segfault for ping -R on qemux86 caused by recvmsg() Date: Wed, 15 Dec 2021 10:19:40 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.34 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fweimer at redhat dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org 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 X-BeenThere: glibc-bugs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Glibc-bugs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Dec 2021 10:19:40 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D28349 --- Comment #5 from Florian Weimer --- (In reply to Fabian Vogt from comment #3) > (In reply to Florian Weimer from comment #2) > > (In reply to Fabian Vogt from comment #1) > > > I encountered the same bug and narrowed it down to recvmsg corrupting= the > > > cmsg buffer due to several bugs in the added __convert_scm_timestamps > > > function. I'm working on a patch to address those. > >=20 > > Would you be able to help reviewing these patches? > >=20 > > [PATCH v3 0/2] Fix 64-bit time_t ancillary socket conversion > > https://sourceware.org/pipermail/libc-alpha/2021-December/134088.html > >=20 > > I believe they are related. >=20 > The linked patch fixes one of the bugs I found, but not another one. What= 's > the way to proceed there, send a patch with just the missing fix? Comment on the mailing list thread and take it from there, I would say. (In reply to Fabian Vogt from comment #4) > BTW: After clicking on "Save Changes" to add a comment on this bug, I end= up > on the page for bug 28350 for some reason. Does anyone else have that wei= rd > behaviour? By default, Bugzilla switches to the next bug in your search results. It's something you can configure under Preferences (under =E2=80=9CAfter changin= g a bug=E2=80=9D). --=20 You are receiving this mail because: You are on the CC list for the bug.=