public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/32126] readdir64_r: Do not skip entries with zero d_ino values Date: Fri, 30 Aug 2024 08:20:05 +0000 [thread overview] Message-ID: <bug-32126-131-vq5j7jvAEB@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-32126-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=32126 Sam James <sam at gentoo dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sam at gentoo dot org -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-08-30 8:20 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-08-30 6:53 [Bug libc/32126] New: " fweimer at redhat dot com 2024-08-30 6:55 ` [Bug libc/32126] " fweimer at redhat dot com 2024-08-30 8:20 ` sam at gentoo dot org [this message] 2024-09-21 17:37 ` cvs-commit at gcc dot gnu.org 2024-09-21 17:38 ` fweimer at redhat dot com
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-32126-131-vq5j7jvAEB@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: linkBe 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).