bug#40509: Use of fsetxattr() in cp tickles an EXT leak (possibly unnecessarily so)

2020-04-15 Thread Gregg Leventhal
Sure that’s fine (regarding copyright), just let me know what to fill out please. On Wed, Apr 15, 2020 at 6:55 PM Paul Eggert wrote: > On 4/15/20 7:11 AM, Gregg Leventhal wrote: > > > +xattr_size = flistxattr(src_fd, list, size); > > +if ( xattr_size || errno == ERANGE ) > > Surely this

bug#40509: Use of fsetxattr() in cp tickles an EXT leak (possibly unnecessarily so)

2020-04-15 Thread Paul Eggert
On 4/15/20 7:11 AM, Gregg Leventhal wrote: +xattr_size = flistxattr(src_fd, list, size); +if ( xattr_size || errno == ERANGE ) Surely this should be 'if (flistxattr (src_fd, NULL, 0) < 0 && errno == ERANGE)'. If you agree with this direction, I can continue, addressing other

bug#40509: Use of fsetxattr() in cp tickles an EXT leak (possibly unnecessarily so)

2020-04-15 Thread Gregg Leventhal
Paul, Your understanding is correct. The problem in cp is that it uses acl_get_fd or acl_get_file which will always return an ACL on EXT4, therefore contriving an ACL to set on the target when it doesn't exist on the source. This causes an extraneous fsetxattr, and hits several arguably

bug#40551: tail: unrecognized file system type 0x794c7630 for /path/to/nginx/error.log'

2020-04-15 Thread Bernhard Voelker
tag 40551 notabug close 40551 stop Hello, On 2020-04-11 10:20, 王群强 wrote: > hi , > I am using " tail -f error.log " command in k8s pod environment, thus i > got a fatal error bellow : > > error message === > tail: unrecognized file system type 0x794c7630 for 'error.log'. please > report