From: Mike Galbraith <efault@gmx.de>
To: Vlastimil Babka <vbabka@suse.cz>, Clark Williams <williams@redhat.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] v5.14-rc5-rt8
Date: Sun, 15 Aug 2021 05:13:11 +0200 [thread overview]
Message-ID: <0044f090d3919eef03048527f1baa34aec5198a8.camel@gmx.de> (raw)
In-Reply-To: <96ceab8e-4bf9-147a-e931-848676003c3f@suse.cz>
On Sat, 2021-08-14 at 21:08 +0200, Vlastimil Babka wrote:
> On 8/12/21 11:44 PM, Clark Williams wrote:
> >
> > $ ./scripts/faddr2line /data/o/linux-5.14.y-rt/vmlinux ___slab_alloc+0x340/0x940
> > ___slab_alloc+0x340/0x940:
> > PageSlabPfmemalloc at include/linux/page-flags.h:814
> > (inlined by) pfmemalloc_match at mm/slub.c:2772
> > (inlined by) ___slab_alloc at mm/slub.c:2874
>
> Aha! That's helpful. Hopefully it's just a small issue where we
> opportunistically test flags on a page that's protected by the local
> lock we didn't take yet, and I didn't realize there's the VM_BUG_ON
> which can trigger if our page went away (which we would have realized
> after taking the lock).
>
> So hopefully the below diff with uninspired naming should help?
I bet a nickle it does, shall let box slave away testing that theory
while its master pedals around the sunny Bavarian countryside.
-Mike
next prev parent reply other threads:[~2021-08-15 3:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 16:37 [ANNOUNCE] v5.14-rc5-rt8 Sebastian Andrzej Siewior
2021-08-12 20:18 ` Clark Williams
2021-08-12 20:45 ` Vlastimil Babka
2021-08-12 21:24 ` Clark Williams
2021-08-12 21:30 ` Vlastimil Babka
2021-08-12 21:44 ` Clark Williams
2021-08-14 19:08 ` Vlastimil Babka
2021-08-15 3:13 ` Mike Galbraith [this message]
2021-08-15 9:01 ` Mike Galbraith
2021-08-15 4:17 ` Mike Galbraith
2021-08-15 9:35 ` Vlastimil Babka
2021-08-15 13:03 ` Mike Galbraith
2021-08-12 21:36 ` Vlastimil Babka
2021-08-12 21:47 ` Clark Williams
2021-08-13 10:56 ` Mike Galbraith
2021-08-14 5:33 ` Mike Galbraith
2021-08-14 18:28 ` Vlastimil Babka
2021-08-15 1:26 ` Mike Galbraith
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=0044f090d3919eef03048527f1baa34aec5198a8.camel@gmx.de \
--to=efault@gmx.de \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--cc=williams@redhat.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).