* linux-next: possible bug in 'block: remove the BIO_NULL_MAPPED flag'
@ 2020-09-23 12:52 Marc Hartmayer
2020-09-23 14:54 ` Christoph Hellwig
0 siblings, 1 reply; 2+ messages in thread
From: Marc Hartmayer @ 2020-09-23 12:52 UTC (permalink / raw)
To: Christoph Hellwig, Jens Axboe, Linux Next Mailing List
Cc: Christian Borntraeger, Marc Hartmayer, Kernel Mailing List,
Linux Block Mailing List, Linux SCSI Mailing List
Hi Christoph, Jens,
I found an interesting bug in my KVM guest (tested on s390x). The guest
uses a virtio-scsi disk and the current linux-next kernel. The problem
is that I cannot get the SCSI ID of the attached SCSI disk. Running the
command `lsscsi --scsi_id` in the guest returns:
root@qemus390x:~# lsscsi --scsi_id
[0:0:0:0] disk Linux scsi_debug 0190 /dev/sda -
but the expected result is something like:
root@qemus390x:~# lsscsi --scsi_id
[0:0:0:0] disk Linux scsi_debug 0190 /dev/sda 33333333000002710
Also there is no /dev/disk/by-id/scsi-* path created. I bisected the
problem to...
commit f3256075ba49d80835b601bfbff350a2140b2924 (HEAD, refs/bisect/bad)
Author: Christoph Hellwig <hch@lst.de>
Date: Thu Aug 27 17:37:45 2020 +0200
block: remove the BIO_NULL_MAPPED flag
When I reverted this commit the problem was gone. Any ideas what the
problem is? Thanks in advance.
Best regards,
Marc
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-09-23 14:54 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-09-23 12:52 linux-next: possible bug in 'block: remove the BIO_NULL_MAPPED flag' Marc Hartmayer
2020-09-23 14:54 ` Christoph Hellwig
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).