From: Heiko Carstens <hca@linux.ibm.com>
To: Liam Howlett <liam.howlett@oracle.com>
Cc: Sven Schnelle <svens@linux.ibm.com>,
Guenter Roeck <linux@roeck-us.net>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mapletree-vs-khugepaged
Date: Tue, 17 May 2022 13:53:22 +0200 [thread overview]
Message-ID: <YoOMsmq24FWsWWyr@osiris> (raw)
In-Reply-To: <20220513165955.mkg5wvfi4dwpzoer@revolver>
On Fri, May 13, 2022 at 05:00:31PM +0000, Liam Howlett wrote:
> * Sven Schnelle <svens@linux.ibm.com> [220513 10:46]:
> > Heiko Carstens <hca@linux.ibm.com> writes:
> > > FWIW, same on s390 - linux-next is completely broken. Note: I didn't
> > > bisect, but given that the call trace, and even the failing address
> > > match, I'm quite confident it is the same reason.
> > IS that issue supposed to be fixed? git bisect pointed me to
> >
> > # bad: [76535d42eb53485775a8c54ea85725812b75543f] Merge branch
> > 'mm-everything' of
> > git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> >
> > which isn't really helpful.
> >
> > Anything we could help with debugging this?
>
> I tested the maple tree on top of the s390 as it was the same crash and
> it was okay. I haven't tested the mm-everything branch though. Can you
> test mm-unstable?
>
> I'll continue setting up a sparc VM for testing here and test
> mm-everything on that and the s390
So due to reports here I did some sort of "special bisect": with today's
linux-next I did a hard reset to commit 562340595cbb ("Merge branch
'for-next/kspp' of
git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git"),
started a bisect on Andrew's tree between mm-stable and mm-unstable, and
merged whatever commit was about to be bisected into 562340595cbb.
This lead finally to commit f1297d3a2cb7 ("mm/mmap: reorganize munmap to
use maple states") as "first bad commit".
So given that we are shortly before the merge window and linux-next is
completely broken for s390, how do we proceed? Right now I have no idea if
there is anything else in linux-next that would break s390 because of this.
Even though I'm sure you won't like to hear this, but I'd appreciate if
this code could be removed from linux-next again.
next prev parent reply other threads:[~2022-05-17 11:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 17:20 [PATCH] mapletree-vs-khugepaged Guenter Roeck
2022-04-28 19:27 ` Liam Howlett
2022-04-29 12:09 ` Heiko Carstens
2022-04-29 13:01 ` Liam Howlett
2022-04-29 13:10 ` Heiko Carstens
2022-04-29 16:18 ` Liam Howlett
2022-05-02 9:10 ` Geert Uytterhoeven
2022-05-13 14:46 ` Sven Schnelle
2022-05-13 14:51 ` Sven Schnelle
2022-05-13 16:49 ` Andrew Morton
2022-05-13 17:00 ` Liam Howlett
2022-05-15 20:02 ` Sven Schnelle
2022-05-16 14:02 ` Liam Howlett
2022-05-16 15:37 ` Sven Schnelle
2022-05-16 15:50 ` Liam Howlett
2022-05-16 17:10 ` Sven Schnelle
2022-05-17 14:52 ` Liam Howlett
2022-05-17 11:53 ` Heiko Carstens [this message]
2022-05-17 12:26 ` Heiko Carstens
2022-05-17 13:23 ` Guenter Roeck
2022-05-17 15:03 ` Liam Howlett
2022-05-17 16:28 ` Guenter Roeck
2022-05-17 20:38 ` Liam Howlett
2022-05-17 14:32 ` Guenter Roeck
2022-05-19 14:35 ` Liam Howlett
2022-05-19 21:41 ` Guenter Roeck
2022-05-19 22:38 ` Liam Howlett
2022-05-30 17:38 ` Liam Howlett
2022-05-31 18:56 ` Liam Howlett
2022-06-01 19:06 ` Liam Howlett
2022-05-13 17:28 ` Guenter Roeck
2022-05-13 20:12 ` Yang Shi
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=YoOMsmq24FWsWWyr@osiris \
--to=hca@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@roeck-us.net \
--cc=svens@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).