Re: du no longer handles errors gracefully

[Jim Meyering]

Andreas Schwab <address@hidden> wrote:

> Jim Meyering <address@hidden> writes:
>
>> Mike Frysinger <address@hidden> wrote:
>>> when encountering dirs missing the executable bit, du used to spit out an
>>> error but continue on its way ... with the new version though, the error
>>> forces premature failure with an helpful message :(
>>>
>>> for example, this dir structure as a non-root user:
>>> rm -rf foo
>>> mkdir -p foo/{a,b,c}
>>> touch foo/a/asdf
>>>
>>> here is coreutils-5.94:
>>> $ du
>>> du: `./b': Permission denied
>>> 1       ./c
>>> 1       ./a
>>> 3       .
>>>
>>> here is coreutils-6.4:
>>> $ du
>>> du: fts_read failed: Permission denied
>>
>> Thanks for the report, but I cannot reproduce that.
>> Here's what I've done (as non-root, with a 2.6.18-based kernel):
>
> I can reproduce that with 2.6.18.1 and 2.6.16.21.  The actual syscall that
> fails is openat(5, "..", ...) with fd 5 opened on "b".  Filesystem does
> not matter.

Ah!  Thanks.
Then you must be using libc-2.4 or newer, right?