linux-kernel - Re: Kernel panic with 4.16-rc1 (and 4.16-rc2) running selftest

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <96bf4941-17c0-0796-292c-b66087f5f52e@infradead.org>
Date:   Fri, 23 Feb 2018 16:27:01 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Cong Wang <xiyou.wangcong@...il.com>
Cc:     Khalid Aziz <khalid.aziz@...cle.com>,
        LKML <linux-kernel@...r.kernel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Matthew Wilcox <matthew@....cx>
Subject: Re: Kernel panic with 4.16-rc1 (and 4.16-rc2) running selftest

[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@...il.com> wrote:
>> On Fri, Feb 23, 2018 at 11:00 AM, Randy Dunlap <rdunlap@...radead.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