linux-ext4 - Re: [PATCH] ext4: Fail unaligned direct IO write with EINVAL

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: <175892300643.128029.2423032449227240852.b4-ty@mit.edu>
Date: Fri, 26 Sep 2025 17:47:36 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: Jan Kara <jack@...e.cz>
Cc: "Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org,
        Ritesh Harjani <ritesh.list@...il.com>
Subject: Re: [PATCH] ext4: Fail unaligned direct IO write with EINVAL


On Mon, 01 Sep 2025 13:27:40 +0200, Jan Kara wrote:
> Commit bc264fea0f6f ("iomap: support incremental iomap_iter advances")
> changed the error handling logic in iomap_iter(). Previously any error
> from iomap_dio_bio_iter() got propagated to userspace, after this commit
> if ->iomap_end returns error, it gets propagated to userspace instead of
> an error from iomap_dio_bio_iter(). This results in unaligned writes to
> ext4 to silently fallback to buffered IO instead of erroring out.
> 
> [...]

Applied, thanks!

[1/1] ext4: Fail unaligned direct IO write with EINVAL
      commit: 963845748fe67125006859229487b45485564db7

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