From: Amir Goldstein <amir73il@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Theodore Tso <tytso@mit.edu>, fstests <fstests@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@kernel.org>, Qian Cai <cai@lca.pw>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux MM <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 5.4-rc1 boot regression with kmemleak enabled
Date: Tue, 5 Nov 2019 21:26:25 +0200 [thread overview]
Message-ID: <CAOQ4uxjwSokr=8K02AOVkjb7UK_qCccQ8gAaEnh116oKSeEn6A@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1911051948350.1869@nanos.tec.linutronix.de>
On Tue, Nov 5, 2019 at 8:49 PM Thomas Gleixner <tglx@linutronix.de> wrote:
>
> On Tue, 5 Nov 2019, Catalin Marinas wrote:
> > On Tue, Nov 05, 2019 at 08:17:11PM +0200, Amir Goldstein wrote:
> > > [ 0.027836] RIP: 0010:get_stack_info+0xa7/0x146
> >
> > Ah, it looks very similar to this report:
> >
> > http://lkml.kernel.org/r/20191019114421.GK9698@uranus.lan
> >
> > Thomas had a patch here:
> >
> > https://lore.kernel.org/linux-mm/alpine.DEB.2.21.1910231950590.1852@nanos.tec.linutronix.de/
> >
> > but not sure whether it has hit mainline yet.
>
> It's queued in tip. Will hit Linus tree during the week.
>
Works for me.
Thanks,
Amir.
prev parent reply other threads:[~2019-11-05 19:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 7:14 5.4-rc1 boot regression with kmemleak enabled Amir Goldstein
2019-11-05 9:02 ` Catalin Marinas
2019-11-05 9:23 ` Qian Cai
2019-11-05 11:54 ` Catalin Marinas
2019-11-05 12:33 ` Amir Goldstein
2019-11-05 15:30 ` Catalin Marinas
2019-11-05 18:17 ` Amir Goldstein
2019-11-05 18:22 ` Catalin Marinas
2019-11-05 18:49 ` Thomas Gleixner
2019-11-05 19:26 ` Amir Goldstein [this message]
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='CAOQ4uxjwSokr=8K02AOVkjb7UK_qCccQ8gAaEnh116oKSeEn6A@mail.gmail.com' \
--to=amir73il@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=catalin.marinas@arm.com \
--cc=fstests@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=willy@infradead.org \
/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).