[Bug 270419] Executable files act as if they are empty directories for some operations

From: <bugzilla-noreply_at_freebsd.org>
Date: Thu, 23 Mar 2023 16:30:01 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270419

            Bug ID: 270419
           Summary: Executable files act as if they are empty directories
                    for some operations
           Product: Base System
           Version: 13.1-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: misc
          Assignee: bugs@FreeBSD.org
          Reporter: okiddle@yahoo.co.uk

Appending a slash and either one or two dots to an executable file is not
producing errors about the file not being a directory as it does on FreeBSD 12.
For example. ls -l /bin/df/.. will actually list the contents of /bin.

I might have assumed this was some odd historical quirk but testing FreeBSD
12.3 and 12.4, they don't exhibit this behaviour. I see the issue on 13.1 but
have confirmed that it isn't specific to me or my system.

I found this because a Makefile was checking for the existence of file/. to
test whether something is a file or a directory. For what it's worth, this
works correctly on Solaris and Linux.

-- 
You are receiving this mail because:
You are the assignee for the bug.