From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: nvme boot problems after merge of mm-stable tree into linux-next
Date: Mon, 13 Feb 2023 22:49:37 -0800 [thread overview]
Message-ID: <07c870d3-5d98-ca51-5de8-034abc631673@roeck-us.net> (raw)
In-Reply-To: <20230214172040.60657882@canb.auug.org.au>
On 2/13/23 22:20, Stephen Rothwell wrote:
> Hi Guenter,
>
> On Mon, 13 Feb 2023 20:01:33 -0800 Guenter Roeck <linux@roeck-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.
>
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.
Guenter
next prev parent reply other threads:[~2023-02-14 6:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ed33b9ff-e6f2-dae8-ede6-59dc3c649ece@roeck-us.net>
2023-02-13 17:47 ` Andrew Morton
2023-02-14 2:23 ` Bagas Sanjaya
2023-02-14 4:01 ` Guenter Roeck
2023-02-14 6:20 ` Stephen Rothwell
2023-02-14 6:49 ` Guenter Roeck [this message]
2023-02-14 7:29 ` Bagas Sanjaya
2023-02-26 22:14 ` Stephen Rothwell
2023-02-26 22:53 ` Guenter Roeck
2023-02-26 23:04 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=07c870d3-5d98-ca51-5de8-034abc631673@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox