find command misbehaves on debian with kernel 4.9
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Searching for system-resolved service following the recent
vulnerability disclosure, I came to see a very strange behavior from
find command.
root@localhost:/# find . -name "*systemd-resolved*"
./usr/share/man/man8/systemd-resolved.service.8.gz
./usr/share/man/man8/systemd-resolved.8.gz
The command returns 0 or two lines as output for the first run. But if
I run the command the second time I get:
root@localhost:/# find . -name "*systemd-resolved*"
./usr/share/man/man8/systemd-resolved.service.8.gz
./usr/share/man/man8/systemd-resolved.8.gz
./lib/systemd/systemd-resolved
./lib/systemd/system/systemd-resolved.service.d
./lib/systemd/system/systemd-resolved.service
This means the first time, "find" does not actually find everything.
Also this only happens one time. Running the command next times shows
correct output. I checked this on some other systems with Debian OS
installed. On those with Kernel 4.9+ this exact problem always occurs
but on systems with kernel 3.16 it doesn't happen
finutils version: 4.4.2
- --
Sirus Shahini
Iran University of Science and Technology
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJZVo4rAAoJELUzPfwK/ZGvZF4H/07N9o6aYIG0BUF9awYbJg9E
ZuOpNasjXlCLVXKbedEOHZXlqsYZczr+NLZ/5pUS1lFbcEqdG3bNHg/h+UEa05RT
8cWaUX1w8GUifA7w+awsorAU43V+qdt56v23WPJJIH12NC3QADTP3C1gx6La3ClQ
25Bu544sEOPEK7n2MHFrhv4f0CZe1C5eIJLsgNlv0WRCyuF3OUBRQgh1Ujpt7Id1
wmr5mA4MkdHdLAGh4IeH90P4kfKrPKhsHHuZ0HWSO6fDvh0c9INwdjfopOIvbHPx
BHpr68DqUg+VqhYQbxOy4IAckYOCVAvX8EJOwB9ithMtWJokTohWcn7TUsS2ShE=
=0TDS
-----END PGP SIGNATURE-----
Reply to: