Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <5ffb520f-d86f-be3e-4239-2f31c681ede2@acm.org>
Date:   Fri, 26 Aug 2022 09:29:36 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.11.0
Subject: Re: [syzbot] upstream boot error: BUG: unable to handle kernel paging
 request in blk_mq_map_swqueue
Content-Language: en-US
To:     Aleksandr Nogikh <nogikh@google.com>
Cc:     Dmitry Vyukov <dvyukov@google.com>,
        syzbot <syzbot+ea55456e1ff28ef7f9ff@syzkaller.appspotmail.com>,
        Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org,
        LKML <linux-kernel@vger.kernel.org>, llvm@lists.linux.dev,
        'Aleksandr Nogikh' via syzkaller-bugs 
        <syzkaller-bugs@googlegroups.com>
References: <0000000000004c3b1405e6b7de26@google.com>
 <f70b1cf7-0291-6ebc-68f8-db9c68963255@acm.org>
 <CANp29Y7bgwDzd47E6h8gseYuu5YXF-ABRrhVXFXS-HF7PhF-Dw@mail.gmail.com>
From:   Bart Van Assche <bvanassche@acm.org>
In-Reply-To: <CANp29Y7bgwDzd47E6h8gseYuu5YXF-ABRrhVXFXS-HF7PhF-Dw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 8/26/22 06:15, Aleksandr Nogikh wrote:
> Syzbot would have included the USB mailing list and the USB
> maintainers if it saw that the bug might be related to this subsystem.
> The bot's guess was that it was the BLOCK LAYER subsystem, so it Cc'd
> only the general lists and linux-block@vger.kernel.org
> 
> Is there anything in this bug report that can reliably indicate that
> the bug has to do with USB? If there is, we can definitely adjust our
> guilty subsystem recognition logic.

Hi Aleksandr,
  I may have been to fast with my conclusion that the root cause is in 
the USB subsystem.

Regarding your question, can syzbot inspect the console log and scan for 
"scsi host%d: %s" strings? The text next to the colon comes from the 
SCSI host template "name" member and hence indicates which SCSI LLD 
driver is involved.

Thanks,

Bart.