mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Edward Adam Davis <eadavis@qq.com>,
	hare@suse.de, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	syzbot+fcee6b76cf2e261c51a4@syzkaller.appspotmail.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH V2] block: no show partitions if partno corrupted
Date: Tue, 14 Jan 2025 22:46:20 -0800	[thread overview]
Message-ID: <Z4dZvH5WuOeNTgXg@infradead.org> (raw)
In-Reply-To: <d384b565-0be8-461d-ba8c-0185842c9d9c@kernel.dk>

On Tue, Jan 14, 2025 at 07:16:31AM -0700, Jens Axboe wrote:
> On 1/14/25 1:51 AM, Edward Adam Davis wrote:
> > diff --git a/block/genhd.c b/block/genhd.c
> > index 9130e163e191..8d539a4a3b37 100644
> > --- a/block/genhd.c
> > +++ b/block/genhd.c
> > @@ -890,7 +890,9 @@ static int show_partition(struct seq_file *seqf, void *v)
> >  
> >  	rcu_read_lock();
> >  	xa_for_each(&sgp->part_tbl, idx, part) {
> > -		if (!bdev_nr_sectors(part))
> > +		int partno = bdev_partno(part);
> > +
> > +		if (!bdev_nr_sectors(part) || WARN_ON(partno >= DISK_MAX_PARTS))
> >  			continue;
> >  		seq_printf(seqf, "%4d  %7d %10llu %pg\n",
> >  			   MAJOR(part->bd_dev), MINOR(part->bd_dev),
> 
> This should be a WARN_ON_ONCE(), and please put warn-on's on a separate
> line.

Ummm...

DISK_MAX_PARTS is 256.

bdev_partno reads form bdev->__bd_flags and masks out BD_PARTNO,
which is 255.

In other words we should never be able to get a value bigger than 255
from bdev_partno, so something is really fishy here that a WARN_ON in
the show function won't help with.

Also the fact that the low-level printf code trips over a 8-bit integer
sounds wrong, and if it does for something not caused by say a use
after free higher up we've got another deep problem there.

All of that has nothing to do with show_partition, though.

  parent reply	other threads:[~2025-01-15  6:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-12 18:56 [syzbot] [fs?] KASAN: global-out-of-bounds Read in number syzbot
2025-01-13 12:21 ` Edward Adam Davis
2025-01-13 22:19   ` syzbot
2025-01-14  1:05 ` Edward Adam Davis
2025-01-14  1:38   ` syzbot
2025-01-14  1:30 ` Edward Adam Davis
2025-01-14  2:13   ` syzbot
2025-01-14  2:28 ` [PATCH] block: no show partitions if partno corrupted Edward Adam Davis
2025-01-14  7:21   ` Hannes Reinecke
2025-01-14  8:51     ` [PATCH V2] " Edward Adam Davis
2025-01-14 14:16       ` Jens Axboe
2025-01-14 14:58         ` [PATCH V3] " Edward Adam Davis
2025-01-14 15:02           ` Jens Axboe
2025-01-14 15:15             ` Edward Adam Davis
2025-01-14 15:25               ` Jens Axboe
2025-01-14 15:34                 ` [PATCH V4] " Edward Adam Davis
2025-01-14 16:21                 ` [PATCH V3] " Edward Adam Davis
2025-01-15  6:46         ` Christoph Hellwig [this message]
2025-01-14  5:29 ` [syzbot] [fs?] KASAN: global-out-of-bounds Read in number syzbot

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=Z4dZvH5WuOeNTgXg@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=eadavis@qq.com \
    --cc=hare@suse.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+fcee6b76cf2e261c51a4@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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®