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
| ||
|
Message-ID: <174775151765.432196.17776440436332077240.b4-ty@mit.edu> Date: Tue, 20 May 2025 10:40:20 -0400 From: "Theodore Ts'o" <tytso@....edu> To: linux-ext4@...r.kernel.org, Zhang Yi <yi.zhang@...weicloud.com> Cc: "Theodore Ts'o" <tytso@....edu>, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, adilger.kernel@...ger.ca, jack@...e.cz, wanghaichi0403@...il.com, yi.zhang@...wei.com, libaokun1@...wei.com, yukuai3@...wei.com, yangerkun@...wei.com Subject: Re: [PATCH v2 1/4] ext4: fix out of bounds punch offset On Tue, 06 May 2025 09:20:06 +0800, Zhang Yi wrote: > Punching a hole with a start offset that exceeds max_end is not > permitted and will result in a negative length in the > truncate_inode_partial_folio() function while truncating the page cache, > potentially leading to undesirable consequences. > > A simple reproducer: > > [...] Applied, thanks! [1/4] ext4: fix out of bounds punch offset commit: b5e58bcd79625423487fa3ecba8e8411b5396327 [2/4] ext4: fix incorrect punch max_end commit: 29ec9bed2395061350249ae356fb300dd82a78e7 [3/4] ext4: factor out ext4_get_maxbytes() commit: dbe27f06fa38b9bfc598f8864ae1c5d5831d9992 [4/4] ext4: ensure i_size is smaller than maxbytes commit: 1a77a028a392fab66dd637cdfac3f888450d00af Best regards, -- Theodore Ts'o <tytso@....edu>
Powered by blists - more mailing lists