All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Hartmayer <mhartmay@linux.ibm.com>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	Marc Hartmayer <mhartmay@linux.ibm.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Block Mailing List <linux-block@vger.kernel.org>,
	Linux SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: linux-next: possible bug in 'block: remove the BIO_NULL_MAPPED flag'
Date: Wed, 23 Sep 2020 14:52:59 +0200	[thread overview]
Message-ID: <87tuvo8xjo.fsf@linux.ibm.com> (raw)

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

             reply	other threads:[~2020-09-23 12:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23 12:52 Marc Hartmayer [this message]
2020-09-23 14:54 ` linux-next: possible bug in 'block: remove the BIO_NULL_MAPPED flag' Christoph Hellwig

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=87tuvo8xjo.fsf@linux.ibm.com \
    --to=mhartmay@linux.ibm.com \
    --cc=axboe@kernel.dk \
    --cc=borntraeger@de.ibm.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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.