public inbox for linux-bcachefs@vger.kernel.org
 help / color / mirror / Atom feed
From: Gianfranco Trad <gianf.trad@gmail.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
	skhan@linuxfoundation.org,
	syzbot+089fad5a3a5e77825426@syzkaller.appspotmail.com
Subject: Re: [PATCH] bcachefs: Fix invalid shift in validate_sb_layout()
Date: Thu, 24 Oct 2024 13:51:14 +0200	[thread overview]
Message-ID: <58e3d8a4-9e8b-41d5-a134-d41b38bd7216@gmail.com> (raw)
In-Reply-To: <jaxnjw5ergn7zrnjuzzosgclpmv5st77gtfaj75my3hblufrn2@b4si2orrodw5>

On 24/10/24 13:24, Kent Overstreet wrote:
> On Thu, Oct 24, 2024 at 12:48:30PM +0200, Gianfranco Trad wrote:
>> On 23/10/24 23:30, Gianfranco Trad wrote:
>>> Add check on layout->sb_max_size_bits against BCH_SB_LAYOUT_SIZE_BITS_MAX
>>> to prevent UBSAN shift-out-of-bounds in validate_sb_layout().
>>>
>>> Reported-by: syzbot+089fad5a3a5e77825426@syzkaller.appspotmail.com
>>> Closes: https://syzkaller.appspot.com/bug?extid=089fad5a3a5e77825426
>>> Fixes: 03ef80b469d5 ("bcachefs: Ignore unknown mount options")
>>> Tested-by: syzbot+089fad5a3a5e77825426@syzkaller.appspotmail.com
>>> Signed-off-by: Gianfranco Trad <gianf.trad@gmail.com>
>>> ---
>>>    fs/bcachefs/errcode.h  | 1 +
>>>    fs/bcachefs/super-io.c | 5 +++++
>>>    2 files changed, 6 insertions(+)
>>>
>>> diff --git a/fs/bcachefs/errcode.h b/fs/bcachefs/errcode.h
>>> index 649263516ab1..b6cbd716000b 100644
>>> --- a/fs/bcachefs/errcode.h
>>> +++ b/fs/bcachefs/errcode.h
>>> @@ -222,6 +222,7 @@
>>>    	x(BCH_ERR_invalid_sb_layout,	invalid_sb_layout_type)			\
>>>    	x(BCH_ERR_invalid_sb_layout,	invalid_sb_layout_nr_superblocks)	\
>>>    	x(BCH_ERR_invalid_sb_layout,	invalid_sb_layout_superblocks_overlap)	\
>>> +	x(BCH_ERR_invalid_sb_layout,    invalid_sb_layout_sb_max_size_bits)     \
>>>    	x(BCH_ERR_invalid_sb,		invalid_sb_members_missing)		\
>>>    	x(BCH_ERR_invalid_sb,		invalid_sb_members)			\
>>>    	x(BCH_ERR_invalid_sb,		invalid_sb_disk_groups)			\
>>> diff --git a/fs/bcachefs/super-io.c b/fs/bcachefs/super-io.c
>>> index ce7410d72089..44d0ac9b00dd 100644
>>> --- a/fs/bcachefs/super-io.c
>>> +++ b/fs/bcachefs/super-io.c
>>> @@ -287,6 +287,11 @@ static int validate_sb_layout(struct bch_sb_layout *layout, struct printbuf *out
>>>    		return -BCH_ERR_invalid_sb_layout_nr_superblocks;
>>>    	}
>>> +	if (layout->sb_max_size_bits > BCH_SB_LAYOUT_SIZE_BITS_MAX) {
>>> +		prt_printf(out, "Invalid superblock layout: max_size_bits too high");
>>> +		return -BCH_ERR_invalid_sb_layout_sb_max_size_bits;
>>> +	}
>>> +
>>>    	max_sectors = 1 << layout->sb_max_size_bits;
>>>    	prev_offset = le64_to_cpu(layout->sb_offset[0]);
>>
>> Wondering if this other patch might be considered more correct to prevent
>> shift oob, given also [0]:
> 
> Your first patch looks better, we want to know if we're feeding it
> garbage
> 

Understood. Thanks Kent.
Have a nice day,
--Gian
>>
>> diff --git a/fs/bcachefs/super-io.c b/fs/bcachefs/super-io.c
>> index ce7410d72089..428172897501 100644
>> --- a/fs/bcachefs/super-io.c
>> +++ b/fs/bcachefs/super-io.c
>> @@ -287,7 +287,7 @@ static int validate_sb_layout(struct bch_sb_layout
>> *layout, struct printbuf *out
>>   		return -BCH_ERR_invalid_sb_layout_nr_superblocks;
>>   	}
>>
>> -	max_sectors = 1 << layout->sb_max_size_bits;
>> +	max_sectors = 1 << min(BCH_SB_LAYOUT_SIZE_BITS_MAX,
>> layout->sb_max_size_bits);
>>
>>   	prev_offset = le64_to_cpu(layout->sb_offset[0]);
>>
>> Also this patch was already tested by syzbot [1]
>>
>> [0] 71dac2482ad3c8d4a8b8998a96751f009bad895f ("bcachefs:
>> BCH_SB_LAYOUT_SIZE_BITS_MAX")
>> [1] https://syzkaller.appspot.com/x/log.txt?x=1640b640580000
>>
>> Thanks for your time,
>>
>> -- Gian
>>


  reply	other threads:[~2024-10-24 11:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23 21:30 [PATCH] bcachefs: Fix invalid shift in validate_sb_layout() Gianfranco Trad
2024-10-24 10:48 ` Gianfranco Trad
2024-10-24 11:24   ` Kent Overstreet
2024-10-24 11:51     ` Gianfranco Trad [this message]
2024-10-24 11:23 ` 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=58e3d8a4-9e8b-41d5-a134-d41b38bd7216@gmail.com \
    --to=gianf.trad@gmail.com \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=syzbot+089fad5a3a5e77825426@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