From: Randy Dunlap <rdunlap@infradead.org>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Khalid Aziz <khalid.aziz@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Matthew Wilcox <matthew@wil.cx>
Subject: Re: Kernel panic with 4.16-rc1 (and 4.16-rc2) running selftest
Date: Fri, 23 Feb 2018 16:27:01 -0800 [thread overview]
Message-ID: <96bf4941-17c0-0796-292c-b66087f5f52e@infradead.org> (raw)
In-Reply-To: <CAM_iQpWSRe0t1Dr=7o+1ejULV=F+_Wx1v7yyw=NRBUTYttMxog@mail.gmail.com>
[add Matthew Wilcox; hopefully he can look/see]
On 02/23/2018 04:13 PM, Cong Wang wrote:
> On Fri, Feb 23, 2018 at 3:27 PM, Cong Wang <xiyou.wangcong@gmail.com> wrote:
>> On Fri, Feb 23, 2018 at 11:00 AM, Randy Dunlap <rdunlap@infradead.org> wrote:
>>> [adding netdev]
>>>
>>> On 02/23/2018 08:05 AM, Khalid Aziz wrote:
>>>> I am seeing a kernel panic with 4.16-rc1 and 4.16-rc2 kernels when running selftests
>>>> from tools/testing/selftests. Last messages from selftest before kernel panic are:
>>>>
>> ...
>>>> Same selftest does not cause panic on 4.15. git bisect pointed to commit 6ce711f2750031d12cec91384ac5cfa0a485b60a ("idr: Make 1-based IDRs more efficient").
>>>> Kernel config is attached.
>>
>> Looks like something horribly wrong with u32 key id idr...
>
> Adding a few printk's, I got:
>
> [ 31.231560] requested handle = ffe00000
> [ 31.232426] allocated handle = 0
> ...
> [ 31.246475] requested handle = ffd00000
> [ 31.247555] allocated handle = 1
>
>
> So the bug is here where we can't allocate a specific handle:
>
> err = idr_alloc_u32(&tp_c->handle_idr, ht, &handle,
> handle, GFP_KERNEL);
> if (err) {
> kfree(ht);
> return err;
> }
>
--
~Randy
next prev parent reply other threads:[~2018-02-24 0:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7995f335-ccac-bfdc-bb37-46d0f887c647@oracle.com>
2018-02-23 19:00 ` Kernel panic with 4.16-rc1 (and 4.16-rc2) running selftest Randy Dunlap
2018-02-23 23:27 ` Cong Wang
2018-02-24 0:13 ` Cong Wang
2018-02-24 0:27 ` Randy Dunlap [this message]
[not found] ` <CAFhKne9Dyx1uvRz_9rvCq7mewAbLA5T77P21oBQfOR7JzP_1aQ@mail.gmail.com>
2018-02-24 1:15 ` Fwd: " Matthew Wilcox
2018-02-24 1:49 ` Chris Mi
2018-02-24 2:46 ` Matthew Wilcox
2018-02-26 9:59 ` Chris Mi
2018-02-26 17:05 ` Khalid Aziz
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=96bf4941-17c0-0796-292c-b66087f5f52e@infradead.org \
--to=rdunlap@infradead.org \
--cc=khalid.aziz@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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).