[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <cover.1693909504.git.ojaswin@linux.ibm.com>
Date: Tue, 5 Sep 2023 15:58:00 +0530
From: Ojaswin Mujoo <ojaswin@...ux.ibm.com>
To: linux-ext4@...r.kernel.org, "Theodore Ts'o" <tytso@....edu>
Cc: Ritesh Harjani <riteshh@...ux.ibm.com>,
linux-kernel@...r.kernel.org, Jan Kara <jack@...e.cz>,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>,
linux-fsdevel@...r.kernel.org
Subject: [PATCH 0/1] ext4: Fix stale data exposure caused with dioread_nolock
The detailed report on the issues faced and the root cause can be found
in the commit message. I've intentionally added all the details to
commit message so that it can be tracked in the future, let me know if
its too long and I can try stripping some info.
For this particular fix, I've tested these patches with xfstests -g
quick with:
- 64k block size, 64k pagesize
- 4k blocksize 64k pagesize
- both with and without nodelalloc
and I don't see any regressions. I'll plan to run more tests on this and
report back if I notice anything. Suggestions or ideas are welcome.
Regards,
ojaswin
Ojaswin Mujoo (1):
ext4: Mark buffer new if it is unwritten to avoid stale data exposure
fs/ext4/inode.c | 4 ++++
1 file changed, 4 insertions(+)
--
2.31.1
Powered by blists - more mailing lists