public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fabian@ritter-vogt.de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/28349] Segfault for ping -R on qemux86 caused by recvmsg()
Date: Wed, 15 Dec 2021 10:12:26 +0000 [thread overview]
Message-ID: <bug-28349-131-XjPJ4UgBUW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28349-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28349
--- Comment #3 from Fabian Vogt <fabian@ritter-vogt.de> ---
(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.
>
> Would you be able to help reviewing these patches?
>
> [PATCH v3 0/2] Fix 64-bit time_t ancillary socket conversion
> https://sourceware.org/pipermail/libc-alpha/2021-December/134088.html
>
> I believe they are related.
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?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-12-15 10:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-18 6:18 [Bug libc/28349] New: " yi.zhao at windriver dot com
2021-11-29 19:50 ` [Bug libc/28349] " rwmacleod at gmail dot com
2021-11-29 20:01 ` rwmacleod at gmail dot com
2021-12-15 9:23 ` fabian@ritter-vogt.de
2021-12-15 10:09 ` fweimer at redhat dot com
2021-12-15 10:12 ` fabian@ritter-vogt.de [this message]
2021-12-15 10:13 ` fabian@ritter-vogt.de
2021-12-15 10:19 ` fweimer at redhat dot com
2021-12-15 13:53 ` fabian@ritter-vogt.de
2021-12-22 18:39 ` adhemerval.zanella at linaro dot org
2022-01-28 21:21 ` adhemerval.zanella at linaro dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-28349-131-XjPJ4UgBUW@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).