From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: qasdev <qasdev00@gmail.com>, Heming Zhao <heming.zhao@suse.com>,
mark@fasheh.com, jlbec@evilplan.org
Cc: ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ocfs2: Fix shift-out-of-bounds UBSAN bug in ocfs2_verify_volume()
Date: Tue, 20 Aug 2024 09:12:41 +0800 [thread overview]
Message-ID: <d10a4f92-00f7-48a7-b6fd-e0fa5e8e3013@linux.alibaba.com> (raw)
In-Reply-To: <ZsPrbmbnAgGRgqLw@hostname>
On 8/20/24 9:03 AM, qasdev wrote:
> On Mon, Aug 19, 2024 at 10:52:29AM +0800, Joseph Qi wrote:
>>
>>
>> On 8/18/24 7:43 PM, Heming Zhao wrote:
>>> On 8/16/24 21:41, qasdev wrote:
>>>> From ad1ca2fd2ecf4eb7ec2c76fcbbf34639f0ad87ca Mon Sep 17 00:00:00 2001
>>>> From: Qasim Ijaz <qasdev00@gmail.com>
>>>> Date: Fri, 16 Aug 2024 02:30:25 +0100
>>>> Subject: [PATCH] ocfs2: Fix shift-out-of-bounds UBSAN bug in
>>>> ocfs2_verify_volume()
>>>>
>>
>> The above should be eliminated from patch body.
>>
>>>> This patch addresses a shift-out-of-bounds error in the
>>>> ocfs2_verify_volume() function, identified by UBSAN. The bug was triggered
>>>> by an invalid s_clustersize_bits value (e.g., 1548), which caused the
>>>> expression "1 << le32_to_cpu(di->id2.i_super.s_clustersize_bits)"
>>>> to exceed the limits of a 32-bit integer,
>>>> leading to an out-of-bounds shift.
>>>>
>>>> Reported-by: syzbot <syzbot+f3fff775402751ebb471@syzkaller.appspotmail.com>
>>>> Closes: https://syzkaller.appspot.com/bug?extid=f3fff775402751ebb471
>>>> Tested-by: syzbot <syzbot+f3fff775402751ebb471@syzkaller.appspotmail.com>
>>>> Signed-off-by: Qasim Ijaz <qasdev00@gmail.com>
>>>> ---
>>>> fs/ocfs2/super.c | 8 ++++++--
>>>> 1 file changed, 6 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/fs/ocfs2/super.c b/fs/ocfs2/super.c
>>>> index afee70125ae3..1e43cdca7f40 100644
>>>> --- a/fs/ocfs2/super.c
>>>> +++ b/fs/ocfs2/super.c
>>>> @@ -2357,8 +2357,12 @@ static int ocfs2_verify_volume(struct ocfs2_dinode *di,
>>>> (unsigned long long)bh->b_blocknr);
>>>> } else if (le32_to_cpu(di->id2.i_super.s_clustersize_bits) < 12 ||
>>>> le32_to_cpu(di->id2.i_super.s_clustersize_bits) > 20) {
>>>> - mlog(ML_ERROR, "bad cluster size found: %u\n",
>>>> - 1 << le32_to_cpu(di->id2.i_super.s_clustersize_bits));
>>>> + if (le32_to_cpu(di->id2.i_super.s_clustersize_bits) < 32)
>>>> + mlog(ML_ERROR, "bad cluster size found: %u\n",
>>>> + 1 << le32_to_cpu(di->id2.i_super.s_clustersize_bits));
>>>> + else
>>>> + mlog(ML_ERROR, "invalid cluster size bit value: %u\n",
>>>> + le32_to_cpu(di->id2.i_super.s_clustersize_bits));
>>>
>>> I prefer to use concise code to fix the error.
>>> Do you like below code?
>>> - mlog(ML_ERROR, "bad cluster size found: %u\n",
>>> - 1 << le32_to_cpu(di->id2.i_super.s_clustersize_bits));
>>> + mlog(ML_ERROR, "bad cluster size bit found: %u\n",
>>> + le32_to_cpu(di->id2.i_super.s_clustersize_bits));
>>>
>>
>> Agree. qasdev, Could you please update and send v2?
>>
>> Thanks,
>> Joseph
>
> Thanks for the feedback. After considering the input, I've refined the patch
> to make it more concise. I've updated the patch and included it below:
>
Hi, please send v2 as a standalone thread.
Thanks,
Joseph
next prev parent reply other threads:[~2024-08-20 1:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 13:41 [PATCH] " qasdev
2024-08-18 11:43 ` Heming Zhao
2024-08-19 2:52 ` Joseph Qi
2024-08-20 1:03 ` [PATCH v2] " qasdev
2024-08-20 1:12 ` Joseph Qi [this message]
2024-08-20 1:22 qasdev
2024-08-20 1:27 ` Joseph Qi
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=d10a4f92-00f7-48a7-b6fd-e0fa5e8e3013@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=heming.zhao@suse.com \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=qasdev00@gmail.com \
/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
Powered by JetHome