linux-kernel - Re: [PATCH v2] arm: print alloc free paths for address in registers

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 for Android: free password hash cracker in your pocket

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

Message-ID: <9e517b50-de9d-4191-21d0-08f278091b62@suse.cz>
Date:   Fri, 12 Mar 2021 10:21:07 +0100
From:   Vlastimil Babka <vbabka@...e.cz>
To:     maninder1.s@...sung.com,
        "linux@...linux.org.uk" <linux@...linux.org.uk>,
        "cl@...ux.com" <cl@...ux.com>,
        "penberg@...nel.org" <penberg@...nel.org>,
        "rientjes@...gle.com" <rientjes@...gle.com>,
        "iamjoonsoo.kim@....com" <iamjoonsoo.kim@....com>,
        "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>
Cc:     "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-mm@...ck.org" <linux-mm@...ck.org>,
        AMIT SAHRAWAT <a.sahrawat@...sung.com>,
        Vaneet Narang <v.narang@...sung.com>,
        "Paul E . McKenney" <paulmck@...nel.org>
Subject: Re: [PATCH v2] arm: print alloc free paths for address in registers

On 3/11/21 11:51 AM, Maninder Singh wrote:
> Hi,
> 
>  
> 
>> Instead of your changes to SL*B, could you check mem_dump_obj() and others added
>> by Paul in 5.12-rc1?
> 
>> (+CC Paul, thus not trimming)
> 
>  
> 
> checked mem_dump_obj(), but it only provides path of allocation and not of free.
> 
> /**
>  * mem_dump_obj - Print available provenance information
> 
> ..
> 
>  * if available, the return address and stack trace from the allocation
>  * of that object.
>  */
> void mem_dump_obj(void *object)
> 
> and in case of "Use After Free", Free path is also required.
> 
> So we need to add support for free path in this API if we have to use it.

I think that would make sense.  

> Thanks,
> 
> Maninder Singh
>