From: Ye Bin <yebin10@huawei.com>
To: <tytso@mit.edu>, <adilger.kernel@dilger.ca>,
<linux-ext4@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <jack@suse.cz>,
Ye Bin <yebin10@huawei.com>
Subject: [PATCH -next 0/3] fix potential out of bound read in ext4_fc_replay_scan()
Date: Sat, 24 Sep 2022 15:52:30 +0800 [thread overview]
Message-ID: <20220924075233.2315259-1-yebin10@huawei.com> (raw)
Ye Bin (3):
ext4: introduce EXT4_FC_TAG_BASE_LEN helper
ext4: factor out ext4_fc_get_tl()
ext4: fix potential out of bound read in ext4_fc_replay_scan()
fs/ext4/fast_commit.c | 122 ++++++++++++++++++++++++++++--------------
fs/ext4/fast_commit.h | 3 ++
2 files changed, 84 insertions(+), 41 deletions(-)
--
2.31.1
next reply other threads:[~2022-09-24 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 7:52 Ye Bin [this message]
2022-09-24 7:52 ` [PATCH -next 1/3] ext4: introduce EXT4_FC_TAG_BASE_LEN helper Ye Bin
2022-09-24 7:52 ` [PATCH -next 2/3] ext4: factor out ext4_fc_get_tl() Ye Bin
2022-09-24 7:52 ` [PATCH -next 3/3] ext4: fix potential out of bound read in ext4_fc_replay_scan() Ye Bin
2022-09-30 3:19 ` [PATCH -next 0/3] " Theodore Ts'o
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=20220924075233.2315259-1-yebin10@huawei.com \
--to=yebin10@huawei.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).