linux-kernel - Re: [PATCH] block: fix NPE when resuming SCSI devices using blk-mq

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <62ddc886d005b91bd6a1bd8775259bb0b5cbe2b2.camel@wdc.com>
Date:   Thu, 26 Jul 2018 13:51:48 +0000
From:   Bart Van Assche <Bart.VanAssche@....com>
To:     "ps@....im" <ps@....im>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
        "axboe@...nel.dk" <axboe@...nel.dk>,
        "ming.lei@...hat.com" <ming.lei@...hat.com>
Subject: Re: [PATCH] block: fix NPE when resuming SCSI devices using blk-mq

On Thu, 2018-07-26 at 10:38 +0200, Patrick Steinhardt wrote:
> That still leaves the other problem of broken suspend. I've just
> checked with v4.17.10, and it's still there: as soon as I resume
> from suspend, the kernel oopses and reboots the machine. I guess
> I'll have to do another debugging session and see where it fails
> exactly (and no, this time there are no more changes to the
> kernel tree).

Can you share the kernel oops details before you start running a bisect?

Thanks,

Bart.