From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Qian Cai <cai@lca.pw>,
linux-kernel@vger.kernel.org, dave@stgolabs.net,
manfred@colorfullife.com, mm-commits@vger.kernel.org
Subject: Re: + ipc-convert-ipcs_idr-to-xarray-update.patch added to -mm tree
Date: Fri, 5 Jun 2020 14:20:39 -0700 [thread overview]
Message-ID: <20200605142039.b8a81c08bf5ba34fa0181545@linux-foundation.org> (raw)
In-Reply-To: <20200605201134.GJ19604@bombadil.infradead.org>
On Fri, 5 Jun 2020 13:11:34 -0700 Matthew Wilcox <willy@infradead.org> wrote:
> On Fri, Jun 05, 2020 at 03:58:48PM -0400, Qian Cai wrote:
> > This will trigger,
> >
> > [ 8853.759549] LTP: starting semget05
> > [ 8867.257088] BUG: sleeping function called from invalid context at mm/slab.h:567
> > [ 8867.270259] in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 22556, name: semget05
> > [ 8867.270309] 2 locks held by semget05/22556:
> > [ 8867.270345] #0: 00000000512de7e0 (&ids->rwsem){++++}-{3:3}, at: ipcget+0x4e/0x230
> > [ 8867.270426] #1: 00000000552b9018 (&new->lock){+.+.}-{2:2}, at: ipc_addid+0xf4/0xf50
>
> Did the fix for this not make it into -next?
I don't think I've seen this fix before. And I'm unclear on how it
pertains to the current patch(es) in -mm. And it has no changelog!
Perhaps it would be best to do a formal send of the latest version?
next prev parent reply other threads:[~2020-06-05 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200420181310.c18b3c0aa4dc5b3e5ec1be10@linux-foundation.org>
2020-04-21 5:43 ` mmotm 2020-04-20-22-43 uploaded Andrew Morton
[not found] ` <20200424014753.DfBuzjmzo%akpm@linux-foundation.org>
2020-06-05 19:58 ` + ipc-convert-ipcs_idr-to-xarray-update.patch added to -mm tree Qian Cai
2020-06-05 20:11 ` Matthew Wilcox
2020-06-05 21:20 ` Andrew Morton [this message]
2020-06-10 2:14 ` Matthew Wilcox
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=20200605142039.b8a81c08bf5ba34fa0181545@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mm-commits@vger.kernel.org \
--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).