|
From: | Pádraig Brady |
Subject: | bug#43497: ls exit status on removed directory |
Date: | Sat, 19 Sep 2020 13:50:33 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:80.0) Gecko/20100101 Thunderbird/80.0 |
On 19/09/2020 00:15, Philip Rowlands wrote:
Steps to reproduce: $ mkdir /tmp/abc $ cd /tmp/abc $ rmdir /tmp/abc $ ls What happened: no output, successful exit status What was expected: no output, unsuccessful exit status ls tried to list the contents of . but failed to do so, at least on Linux: open(".", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 3 getdents(3, 0x55e10c419cf0, 32768) = -1 ENOENT (No such file or directory) Although "stat ." and "ls -ld ." still work on the removed directory, should "ls ." report success even though the getdents syscall fails?
What you expect was released as part of v8.32: https://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v8.31-88-g05a99f7d7 though current trunk (and Fedora at least), have reverted to the original behavior: https://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v8.32-2-g10fcb97bd cheers, Pádraig
[Prev in Thread] | Current Thread | [Next in Thread] |