mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hongbo Li <lihongbo22@huawei.com>
To: Jeongjun Park <aha310510@gmail.com>
Cc: <kent.overstreet@linux.dev>, <mmpgouride@gmail.com>,
	<linux-bcachefs@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<syzbot+7f45fa9805c40db3f108@syzkaller.appspotmail.com>
Subject: Re: [PATCH v3] bcachefs: fix shift oob in alloc_lru_idx_fragmentation
Date: Wed, 23 Oct 2024 09:11:01 +0800	[thread overview]
Message-ID: <68aa186e-a6ab-4fd8-bc17-6d131a80636b@huawei.com> (raw)
In-Reply-To: <D983ED6A-1206-4D3F-AAEB-4572BD81AB2B@gmail.com>



On 2024/10/22 12:05, Jeongjun Park wrote:
> 
> 
>> Hongbo Li <lihongbo22@huawei.com> wrote:
>>
>> 
>>
>>> On 2024/10/21 23:43, Jeongjun Park wrote:
>>> The size of a.data_type is set abnormally large, causing shift-out-of-bounds.
>>> To fix this, we need to add validation on a.data_type in
>>> alloc_lru_idx_fragmentation().
>>> Reported-by: syzbot+7f45fa9805c40db3f108@syzkaller.appspotmail.com
>>> Fixes: 260af1562ec1 ("bcachefs: Kill alloc_v4.fragmentation_lru")
>>> Signed-off-by: Jeongjun Park <aha310510@gmail.com>
>>> ---
>>>   fs/bcachefs/alloc_background.h | 3 +++
>>>   1 file changed, 3 insertions(+)
>>> diff --git a/fs/bcachefs/alloc_background.h b/fs/bcachefs/alloc_background.h
>>> index f8e87c6721b1..163a67b97a40 100644
>>> --- a/fs/bcachefs/alloc_background.h
>>> +++ b/fs/bcachefs/alloc_background.h
>>> @@ -168,6 +168,9 @@ static inline bool data_type_movable(enum bch_data_type type)
>>>   static inline u64 alloc_lru_idx_fragmentation(struct bch_alloc_v4 a,
>>>                             struct bch_dev *ca)
>>>   {
>>> +    if (a.data_type >= BCH_DATA_NR)
>>> +        return 0;
>>> +
>>
>> oh, I found I have done the same thing in [1]("Re: [syzbot] [bcachefs?] UBSAN: shift-out-of-bounds in bch2_alloc_to_text"). But in my humble opinion, the validation changes also should be added. And in addition, move the condition about a.data_type into data_type_movable will be better. Just my personal opinion.:)
>>
>> [1] https://www.spinics.net/lists/kernel/msg5412619.html
> 
> I still disagree with the fix to make data_type_movable() do the validation,
> but I think [1] is definitely a patch that needs to be added.
> 
> However, [1] is far from preventing the shift oob vulnerability described
> in that syzbot report. Therefore, I think [1] should be written as a
> standalone patch and committed, rather than as a patch for that

I'm fine for this.:)

Thanks,
Hongbo

> syzbot report.
> 
>>
>> Thanks,
>> Hongbo
>>
>>>       if (!data_type_movable(a.data_type) ||
>>>           !bch2_bucket_sectors_fragmented(ca, a))
>>>           return 0;
>>> --

  reply	other threads:[~2024-10-23  1:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21 15:43 Jeongjun Park
2024-10-22  2:26 ` Hongbo Li
2024-10-22  2:38   ` Alan Huang
2024-10-22  3:05     ` Hongbo Li
2024-10-22  3:23       ` Alan Huang
2024-10-22  4:05   ` Jeongjun Park
2024-10-23  1:11     ` Hongbo Li [this message]
2024-10-24 11:30   ` Kent Overstreet
2024-10-24 11:30 ` Kent Overstreet

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=68aa186e-a6ab-4fd8-bc17-6d131a80636b@huawei.com \
    --to=lihongbo22@huawei.com \
    --cc=aha310510@gmail.com \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmpgouride@gmail.com \
    --cc=syzbot+7f45fa9805c40db3f108@syzkaller.appspotmail.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

all inboxes | Powered by JetHome®