bug#11844: du bogus warning with bind mounts

[Jim Meyering]

Jim Meyering wrote:
> [Re: http://bugs.gnu.org/11844
>  du: continue processing after bind-mount induced dir-cycle ]
>
> Ondrej Oprala wrote:
>> Sure, that looks great. Thanks for the help.
>
> I added this to the log:
>
>     * THANKS.in: Update.
>     This implements the proposal in http://bugs.gnu.org/11844.
>     Originally reported in http://bugs.debian.org/563254 by Alan Jenkins
>     and more recently as http://bugzilla.redhat.com/836557
>
> and pushed:
> http://git.sv.gnu.org/cgit/coreutils.git/commit/?id=cf7e1b5b8fb53aef2a9103a32

The "du"-related part of this bug is now resolved,
so I'm marking it "done".

As I mentioned in the proposal, http://bugs.gnu.org/11844:

    I have been considering a fix for this:
      - read+stat all mount points at start-up
          For now, I would do this in du.c, not fts.c, since fts clients
          like rm, chmod, chown, etc. are much less likely to be used to
          process mount points in a recursive traversal.  Eventually, this
          could migrate into fts.c, and be enabled via a new option.  Once
          ls is converted to use fts, we would have two clients using the
          new feature.

Which means until ls.c is converted to use fts.c (a big job)
there's little point in trying to move this functionality into fts.c.