linux-kernel - Re: problem booting 5.10

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]

Date:   Tue, 8 Dec 2020 20:29:22 +0100 (CET)
From:   Julia Lawall <julia.lawall@...ia.fr>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
cc:     "Martin K. Petersen" <martin.petersen@...cle.com>,
        "James E.J. Bottomley" <jejb@...ux.ibm.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        nicolas.palix@...v-grenoble-alpes.fr,
        linux-scsi <linux-scsi@...r.kernel.org>
Subject: Re: problem booting 5.10



On Tue, 8 Dec 2020, Linus Torvalds wrote:

> On Tue, Dec 8, 2020 at 10:59 AM Martin K. Petersen
> <martin.petersen@...cle.com> wrote:
> >
> > > So I'm adding SCSI people to the cc, just in case they go "Hmm..".
> >
> > Only change in this department was:
> >
> > 831e3405c2a3 scsi: core: Don't start concurrent async scan on same host
>
> Yeah, I found that one too, and dismissed it for the same reason you
> did - it wasn't in rc1. Plus it looked very simple.
>
> That said, maybe Julia might have misspoken, and rc1 was ok,

rc1 was not ok.  I just started rebasing and the first step was not ok
either.

> so I
> guess it's possible. The scan_mutex does show up in that "locks held"
> list, although I can't see why it would matter. But it does
> potentially change timing (so it could expose some existing race), if
> nothing else.
>
> But let's make sure Jens is aware of this too, in case it's some ATA
> issue. Not that any of those handful of 5.10 changes look remotely
> likely _either_.
>
> Jens, see
>
>    https://lore.kernel.org/lkml/alpine.DEB.2.22.394.2012081813310.2680@hadrien/
>
> if you don't already have the lkml thread locally.. There's not enough
> of the dmesg to even really guess what Julia's actual hardware is,
> apart from it being a Seagate SATA disk. Julia? What controllers and
> disks do you have show up when things work?

A dmesg after successfully booting in 5.9 is attached.

julia
Download attachment "info.gz" of type "application/gzip" (31057 bytes)