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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20230214172040.60657882@canb.auug.org.au>
Date:   Tue, 14 Feb 2023 17:20:40 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     Bagas Sanjaya <bagasdotme@...il.com>,
        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

Hi Guenter,

On Mon, 13 Feb 2023 20:01:33 -0800 Guenter Roeck <linux@...ck-us.net> wrote:
>
> Overall, that suggests that there may have been a change somewhere
> else in the kernel which is incompatible with a change in one of
> the mm branches. It is interesting that the problem in next-20230210
> was seen after the merge of mm-stable, and that it is now seen after
> the merge of mm-everything.

That could be because I moved some merge resolution fix patches from
the merge of mm-everything to the merge of mm-stable (they were all for
conflicts involving commits that are now in mm-stable).  So one of my
merge resolutions could be bad.  Or there could be some interaction of
something in mm-everything (that is not in mm-stable or
mm-nonmm-stable) that is interacting with some other change in the rest
of -next.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped