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: <169661554698.173366.728941842508344201.b4-ty@mit.edu> Date: Fri, 6 Oct 2023 14:06:23 -0400 From: "Theodore Ts'o" <tytso@....edu> To: linux-ext4@...r.kernel.org, Ojaswin Mujoo <ojaswin@...ux.ibm.com> Cc: "Theodore Ts'o" <tytso@....edu>, Ritesh Harjani <ritesh.list@...il.com>, linux-kernel@...r.kernel.org, Jan Kara <jack@...e.cz> Subject: Re: [PATCH v3 0/1] ext4: Fix stale data exposure caused with dioread_nolock On Mon, 18 Sep 2023 16:15:49 +0530, Ojaswin Mujoo wrote: > ** Changes in v3 ** > > - Removed accidental "---" separator in commit message. > - Picked up Jan's Reviewed by. > - v2: > https://lore.kernel.org/linux-ext4/cover.1694860198.git.ojaswin@linux.ibm.com/ > > [...] Applied, thanks! [1/1] ext4: Mark buffer new if it is unwritten to avoid stale data exposure commit: 2cd8bdb5efc1e0d5b11a4b7ba6b922fd2736a87f Best regards, -- Theodore Ts'o <tytso@....edu>
Powered by blists - more mailing lists