linux-kernel - Re: nvme boot problems after merge of mm-stable tree into linux-next

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 for Android: free password hash cracker in your pocket

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

Message-ID: <d4260bee-2bec-40e4-b07f-3a9fa18c3d72@roeck-us.net>
Date:   Sun, 26 Feb 2023 14:53:29 -0800
From:   Guenter Roeck <linux@...ck-us.net>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Bagas Sanjaya <bagasdotme@...il.com>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
        linux-mm@...ck.org
Subject: Re: nvme boot problems after merge of mm-stable tree into linux-next

On 2/26/23 14:14, Stephen Rothwell wrote:
> Hi all,
> 
> On Tue, 14 Feb 2023 14:29:29 +0700 Bagas Sanjaya <bagasdotme@...il.com> wrote:
>>
>> On 2/14/23 13:49, Guenter Roeck wrote:
>>> In next-20230210, the crash happened after the merge of mm-stable.
>>> In next-20230213, the crash happens after the merge of mm-everything.
>>> That means both the merge of mm-stable and mm-nonmm-stable are now fine.
>>> So I would suspect that something in the merge of mm-everything
>>> interacts with the rest of -next.
>>>    
>>
>> OK, thanks!
> 
> Did this get resolved?
> 

I think so. Either the offending patch was reverted, or it has been fixed.
I still see various boot problems in -next (and most of them are now
seen in mainline as well), but none of them are nvme related.

Guenter