linux-ext4 - Re: [PATCH] ext4: Avoid crash when inline data creation follows DIO write

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>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <166431556705.3511882.4814006809885292570.b4-ty@mit.edu>
Date:   Tue, 27 Sep 2022 17:53:32 -0400
From:   "Theodore Ts'o" <tytso@....edu>
To:     jack@...e.cz
Cc:     "Theodore Ts'o" <tytso@....edu>, tadeusz.struk@...aro.org,
        syzbot+bd13648a53ed6933ca49@...kaller.appspotmail.com,
        linux-ext4@...r.kernel.org
Subject: Re: [PATCH] ext4: Avoid crash when inline data creation follows DIO write

On Wed, 27 Jul 2022 17:57:53 +0200, Jan Kara wrote:
> When inode is created and written to using direct IO, there is nothing
> to clear the EXT4_STATE_MAY_INLINE_DATA flag. Thus when inode gets
> truncated later to say 1 byte and written using normal write, we will
> try to store the data as inline data. This confuses the code later
> because the inode now has both normal block and inline data allocated
> and the confusion manifests for example as:
> 
> [...]

Applied, thanks!

[1/1] ext4: Avoid crash when inline data creation follows DIO write
      commit: 4331037750fdd4c698facc8a03075f88f15ffbe6

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