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] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 16 Apr 2019 13:37:48 +0200
From:   Vlastimil Babka <>
To:     Thomas Gleixner <>,
        Andy Lutomirski <>
Cc:     Josh Poimboeuf <>,
        LKML <>, X86 ML <>,
        Sean Christopherson <>,
        Andrew Morton <>,
        Pekka Enberg <>,
        Linux-MM <>,
        David Rientjes <>
Subject: Re: [patch V4 01/32] mm/slab: Fix broken stack trace storage

On 4/15/19 11:22 PM, Thomas Gleixner wrote:
> On Mon, 15 Apr 2019, Andy Lutomirski wrote:
>> On Mon, Apr 15, 2019 at 9:17 AM Josh Poimboeuf <> wrote:
>>> On Mon, Apr 15, 2019 at 06:07:44PM +0200, Thomas Gleixner wrote:
>>>>> Looks like stack_trace.nr_entries isn't initialized?  (though this code
>>>>> gets eventually replaced by a later patch)
>>>> struct initializer initialized the non mentioned fields to 0, if I'm not
>>>> totally mistaken.
>>> Hm, it seems you are correct.  And I thought I knew C.
>>>>> Who actually reads this stack trace?  I couldn't find a consumer.
>>>> It's stored directly in the memory pointed to by @addr and that's the freed
>>>> cache memory. If that is used later (UAF) then the stack trace can be
>>>> printed to see where it was freed.
>>> Right... but who reads it?
>> That seems like a reasonable question.  After some grepping and some
>> git searching, it looks like there might not be any users.  I found
> Anymore. There was something 10y+ ago.

In theory it can be useful in a crash dump. But I don't see any related
check that would trigger a panic, in order to get one.

>> SLAB_STORE_USER, but that seems to be independent.
>> So maybe the whole mess should just be deleted.  If anyone ever
>> notices, they can re-add it better.
> No objections from my side, but the mm people might have opinions.

Anyone who wants to debug wrong slab usage probably uses SLUB anyway, so
I don't think it's a problem to remove broken SLAB debugging. Perhaps
even SLAB itself will be removed soon if there's performance data
supporting it [1].


> Thanks,
> 	tglx

Powered by blists - more mailing lists