linux-ext4 - Re: [PATCH] ext4: correct inline offset when handling xattrs in inode body

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 13 Jul 2023 10:55:06 -0400
From:   "Theodore Ts'o" <tytso@....edu>
To:     linux-ext4@...r.kernel.org, Eric Whitney <enwlinux@...il.com>
Cc:     "Theodore Ts'o" <tytso@....edu>
Subject: Re: [PATCH] ext4: correct inline offset when handling xattrs in inode body


On Mon, 22 May 2023 14:15:20 -0400, Eric Whitney wrote:
> When run on a file system where the inline_data feature has been
> enabled, xfstests generic/269, generic/270, and generic/476 cause ext4
> to emit error messages indicating that inline directory entries are
> corrupted.  This occurs because the inline offset used to locate
> inline directory entries in the inode body is not updated when an
> xattr in that shared region is deleted and the region is shifted in
> memory to recover the space it occupied.  If the deleted xattr precedes
> the system.data attribute, which points to the inline directory entries,
> that attribute will be moved further up in the region.  The inline
> offset continues to point to whatever is located in system.data's former
> location, with unfortunate effects when used to access directory entries
> or (presumably) inline data in the inode body.
> 
> [...]

Applied, thanks!

[1/1] ext4: correct inline offset when handling xattrs in inode body
      commit: 48ef88508c16866ec9641fdda38642aa1f776fd4

Best regards,
-- 
Theodore Ts'o <tytso@....edu>