From: Guenter Roeck <linux@roeck-us.net>
To: Christoph Hellwig <hch@lst.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: Linux 5.14-rc1
Date: Mon, 12 Jul 2021 06:53:32 -0700 [thread overview]
Message-ID: <0cf6d000-f886-4e99-2e80-78da4ae9367d@roeck-us.net> (raw)
In-Reply-To: <20210712052046.GB8042@lst.de>
On 7/11/21 10:20 PM, Christoph Hellwig wrote:
> On Sun, Jul 11, 2021 at 09:14:23PM -0700, Guenter Roeck wrote:
>> My guess was correct. Bisect points to the above commit. Bisect log as well
>> as complete backtrace and example qemu command attached.
>>
>> Copying Christoph and Jens.
>
> This should fіx it:
>
> diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
> index 6d2d63629a90..b8d55af763f9 100644
> --- a/drivers/scsi/sd.c
> +++ b/drivers/scsi/sd.c
> @@ -98,11 +98,7 @@ MODULE_ALIAS_SCSI_DEVICE(TYPE_MOD);
> MODULE_ALIAS_SCSI_DEVICE(TYPE_RBC);
> MODULE_ALIAS_SCSI_DEVICE(TYPE_ZBC);
>
> -#if !defined(CONFIG_DEBUG_BLOCK_EXT_DEVT)
> #define SD_MINORS 16
> -#else
> -#define SD_MINORS 0
> -#endif
>
> static void sd_config_discard(struct scsi_disk *, unsigned int);
> static void sd_config_write_same(struct scsi_disk *);
>
Yes, that fixes the problem for me.
Tested-by: Guenter Roeck <linux@roeck-us.net>
Thanks,
Guenter
next prev parent reply other threads:[~2021-07-12 13:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-11 22:49 Linus Torvalds
2021-07-12 1:56 ` Guenter Roeck
2021-07-12 4:14 ` Guenter Roeck
2021-07-12 5:20 ` Christoph Hellwig
2021-07-12 13:53 ` Guenter Roeck [this message]
2021-07-12 19:03 ` Linus Torvalds
2021-07-12 19:24 ` Christoph Hellwig
2021-07-12 19:27 ` Linus Torvalds
2021-07-12 19:28 ` Guenter Roeck
2021-07-12 7:08 ` Jon Masters
2021-07-12 19:14 ` Linus Torvalds
2021-07-12 19:22 ` Christian König
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=0cf6d000-f886-4e99-2e80-78da4ae9367d@roeck-us.net \
--to=linux@roeck-us.net \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--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 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®