public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stephane+sourceware at chazelas dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug glob/25659] glob("/foo/*/") may also match regular & other kind of files, not just directories Date: Sat, 13 Mar 2021 08:52:14 +0000 [thread overview] Message-ID: <bug-25659-131-l38cC0GRxy@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25659-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25659 Stephane Chazelas <stephane+sourceware at chazelas dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stephane+sourceware@chazela | |s.org --- Comment #1 from Stephane Chazelas <stephane+sourceware at chazelas dot org> --- Note that it was reported at https://unix.stackexchange.com/questions/638955/what-could-be-a-cause-for-getdents-returning-different-results-on-2-systems, there about a "prl_fs" filesystem (likely related to some Parallel virtualisation software). I can reproduce it with glibc 2.33, and also with broken symlinks: $ mkdir -p testdir/dir $ ln -s /no/such/file testdir/broken $ ./glob 'testdir/*/' testdir/broken testdir/dir/ Note that while the issue can be reproduced with ./*/ or b*/, I can't reproduce it with */ $ cd testdir $ ../glob './*/' ./broken ./dir/ $ ../glob 'b*/' broken $ ../glob '*/' dir/ -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-13 8:52 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-12 7:45 [Bug glob/25659] New: " spagoveanu at gmail dot com 2021-03-13 8:52 ` stephane+sourceware at chazelas dot org [this message] 2021-03-13 9:16 ` [Bug glob/25659] " gadelat at gmail dot com 2023-02-27 15:35 ` schwab@linux-m68k.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-25659-131-l38cC0GRxy@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).