lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Wed, 29 Jan 2020 16:32:29 +0100
From:   Herbert Poetzl <herbert@...hfloor.at>
To:     linux-ext4@...r.kernel.org
Subject: comm setfattr: corrupted xattr entries on 'clean' filesystem


Not sure this is the best place for this, but it was
suggest on #linuxfs to report the problem here ...

I have an (older) ext3 filesystem where 'some' files
are unable to accept any extended attributes (xattrs).

 # setfattr -n user.x -v y some-file

... results in ...

 setfattr: some-file: Structure needs cleaning

... and the kernel reports ...

kernel: EXT4-fs error (device md2): ext4_xattr_set_entry:1607: inode #2084096: comm setfattr: corrupted xattr entries

... kernel is not the latest (4.19.84), but e2fsck is ...

e2fsck 1.45.5 (07-Jan-2020)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/md2: 6594874/9538640 files (2.7% non-contiguous), 3887814750/3907018432 blocks

Any suggestions how to 'clean my structures' would
be appreciated!

Thanks in advance,
Herbert

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ