All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Marco Elver <elver@google.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	hare@suse.de, martin.petersen@oracle.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [GIT PULL] first round of SCSI updates for the 5.13+ merge window
Date: Tue, 6 Jul 2021 17:40:56 +0300	[thread overview]
Message-ID: <20210706144056.GE26651@kadam> (raw)
In-Reply-To: <YORh1+8Mk5RYCzx7@elver.google.com>

On Tue, Jul 06, 2021 at 03:59:51PM +0200, 'Marco Elver' via syzkaller-bugs wrote:
> On Fri, Jul 02, 2021 at 09:11AM +0100, James Bottomley wrote:
> [...]
> >       scsi: core: Kill DRIVER_SENSE
> [...]
> 
> As of this being merged, most of our syzbot instances are broken with:
> 
> | Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
> | CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.13.0-syzkaller #0
> | Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
> | Call Trace:
> |  __dump_stack lib/dump_stack.c:79 [inline]
> |  dump_stack_lvl+0x6e/0x91 lib/dump_stack.c:96
> |  panic+0x192/0x4c7 kernel/panic.c:232
> |  mount_block_root+0x268/0x31a init/do_mounts.c:439
> |  mount_root+0x162/0x18d init/do_mounts.c:555
> |  prepare_namespace+0x1ff/0x234 init/do_mounts.c:607
> |  kernel_init_freeable+0x2c4/0x2d6 init/main.c:1604
> |  kernel_init+0x1a/0x1c0 init/main.c:1483
> |  ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
> 
> I've bisected the problem to 464a00c9e0ad ("scsi: core: Kill DRIVER_SENSE"):

Here is one of syzbot reports.

https://groups.google.com/g/syzkaller-bugs/c/6aqmRNRYI7E/m/V7BNerRfDAAJ

If you look at the console output link, init_mount() is failing with
-ENXIO.  It looks the sda drive is not found at all.  It's supposed to
print a list of available partitions but the list is empty.

regards,
dan carpenter


      parent reply	other threads:[~2021-07-06 14:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02  8:11 [GIT PULL] first round of SCSI updates for the 5.13+ merge window James Bottomley
2021-07-02 22:37 ` pr-tracker-bot
2021-07-02 22:46 ` Linus Torvalds
2021-07-06 13:59 ` Marco Elver
2021-07-06 14:27   ` Martin K. Petersen
2021-07-06 14:34     ` Marco Elver
2021-07-06 14:40   ` Dan Carpenter [this message]

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=20210706144056.GE26651@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=elver@google.com \
    --cc=hare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.