linux-kernel - linux-next: possible bug in 'block: remove the BIO_NULL

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <87tuvo8xjo.fsf@linux.ibm.com>
Date:   Wed, 23 Sep 2020 14:52:59 +0200
From:   Marc Hartmayer <mhartmay@...ux.ibm.com>
To:     Christoph Hellwig <hch@....de>, Jens Axboe <axboe@...nel.dk>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Cc:     Christian Borntraeger <borntraeger@...ibm.com>,
        Marc Hartmayer <mhartmay@...ux.ibm.com>,
        Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Block Mailing List <linux-block@...r.kernel.org>,
        Linux SCSI Mailing List <linux-scsi@...r.kernel.org>
Subject: linux-next: possible bug in 'block: remove the BIO_NULL_MAPPED flag'

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@...us390x:~# lsscsi --scsi_id
[0:0:0:0]    disk    Linux    scsi_debug       0190  /dev/sda   -

but the expected result is something like:

root@...us390x:~# 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@....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