From: Matthew Wilcox <willy@infradead.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-fsdevel@vger.kernel.org,
syzbot+1631f09646bc214d2e76@syzkaller.appspotmail.com,
Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
ntfs3@lists.linux.dev, Alexander Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Kari Argillander <kari.argillander@stargateuniverse.net>,
Namjae Jeon <linkinjeon@kernel.org>
Subject: Re: [PATCH] fs/ntfs3: validate BOOT sectors_per_clusters
Date: Fri, 29 Apr 2022 20:11:11 +0100 [thread overview]
Message-ID: <Ymw4T1CF4PxMe5Ym@casper.infradead.org> (raw)
In-Reply-To: <8a29f83c-7fbd-8044-406f-248595cd2ee6@infradead.org>
On Fri, Apr 29, 2022 at 11:52:47AM -0700, Randy Dunlap wrote:
> Hi--
>
> On 4/29/22 10:39, Matthew Wilcox wrote:
> > On Fri, Apr 29, 2022 at 10:27:11AM -0700, Randy Dunlap wrote:
> > > When the NTFS BOOT sectors_per_clusters field is > 0x80,
> > > it represents a shift value. First change its sign to positive
> > > and then make sure that the shift count is not too large.
> > > This prevents negative shift values and shift values that are
> > > larger than the field size.
> > >
> > > Prevents this UBSAN error:
> > >
> > > UBSAN: shift-out-of-bounds in ../fs/ntfs3/super.c:673:16
> > > shift exponent -192 is negative
> > >
> > > Fixes: 82cae269cfa9 ("fs/ntfs3: Add initialization of super block")
> > > Signed-off-by: Randy Dunlap<rdunlap@infradead.org>
> > > Reported-by:syzbot+1631f09646bc214d2e76@syzkaller.appspotmail.com
> > > Cc: Konstantin Komarov<almaz.alexandrovich@paragon-software.com>
> > > Cc:ntfs3@lists.linux.dev
> > > Cc: Alexander Viro<viro@zeniv.linux.org.uk>
> > > Cc: Andrew Morton<akpm@linux-foundation.org>
> > > Cc: Kari Argillander<kari.argillander@stargateuniverse.net>
> > > Cc: Namjae Jeon<linkinjeon@kernel.org>
> > > ---
> > > fs/ntfs3/super.c | 5 +++--
> > > 1 file changed, 3 insertions(+), 2 deletions(-)
> > >
> > > --- linux-next-20220428.orig/fs/ntfs3/super.c
> > > +++ linux-next-20220428/fs/ntfs3/super.c
> > > @@ -670,7 +670,8 @@ static u32 true_sectors_per_clst(const s
> > > {
> > > return boot->sectors_per_clusters <= 0x80
> > > ? boot->sectors_per_clusters
> > > - : (1u << (0 - boot->sectors_per_clusters));
> > > + : -(s8)boot->sectors_per_clusters > 31 ? -1
> > > + : (1u << -(s8)boot->sectors_per_clusters);
> > > }
> > This hurts my brain. Can we do instead:
>
> It's just C. Lot clearer than some of our macro magic.
Well, yeah, but I don't have to understand our macro magic; I can just
assume it does what it says on the tin.
> >
> > if (boot->sectors_per_clusters <= 0x80)
> > return boot->sectors_per_clusters;
> > if (boot->sectors_per_clusters < 0xA0)
>
> The 0xA0 does not take into account the '-' negating of sectors_per_clusters
> in the shift.
> Looks like it should be
>
> if (boot->sectors_per_clusters >= 0xe1)
> return 1U << -boot->sectors_per_clusters;
Oh! I misunderstood how the ranges are used. But I think a unary minus
will leave the type as unsigned (am I wrong? C integer promotions
always confuse me), so how about:
if (boot->sectors_per_clusters > 0xe0)
return 1U << (0 - boot->sectors_per_clusters);
https://en.cppreference.com/w/c/language/conversion
> > return 1U << (boot->sectors_per_clusters - 0x80);
> > return 0xffffffff;
> >
>
> Sorry about your head.
next prev parent reply other threads:[~2022-04-29 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 17:27 [PATCH] fs/ntfs3: validate BOOT sectors_per_clusters Randy Dunlap
2022-04-29 17:39 ` Matthew Wilcox
2022-04-29 17:40 ` Matthew Wilcox
2022-04-29 18:52 ` Randy Dunlap
2022-04-29 19:11 ` Matthew Wilcox [this message]
2022-04-29 19:16 ` Randy Dunlap
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=Ymw4T1CF4PxMe5Ym@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=kari.argillander@stargateuniverse.net \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=rdunlap@infradead.org \
--cc=syzbot+1631f09646bc214d2e76@syzkaller.appspotmail.com \
--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