From: Ojaswin Mujoo <ojaswin@linux.ibm.com>
To: linux-ext4@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>
Cc: Ritesh Harjani <riteshh@linux.ibm.com>,
linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/1] ext4: Fix stale data exposure caused with dioread_nolock
Date: Tue, 5 Sep 2023 15:58:00 +0530 [thread overview]
Message-ID: <cover.1693909504.git.ojaswin@linux.ibm.com> (raw)
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
next reply other threads:[~2023-09-05 15:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 10:28 Ojaswin Mujoo [this message]
2023-09-05 10:28 ` [PATCH 1/1] ext4: Mark buffer new if it is unwritten to avoid stale data exposure Ojaswin Mujoo
2023-09-05 13:56 ` Jan Kara
2023-09-07 7:36 ` Ojaswin Mujoo
2023-09-07 11:46 ` Jan Kara
2023-09-07 19:33 ` Ojaswin Mujoo
2023-09-08 8:38 ` Jan Kara
2023-09-09 7:25 ` Ojaswin Mujoo
2023-09-14 11:54 ` Ojaswin Mujoo
2023-09-14 14:19 ` Jan Kara
2023-09-16 11:02 ` Ojaswin Mujoo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1693909504.git.ojaswin@linux.ibm.com \
--to=ojaswin@linux.ibm.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riteshh@linux.ibm.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).