linux-kernel - Re: [PATCH] mm: Functions used internally should not be put into

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: <9b556b3d-538e-733b-7525-57a78012d3bf@meta.com>
Date:   Sat, 21 Jan 2023 12:34:06 -0800
From:   Yonghong Song <yhs@...a.com>
To:     Rong Tao <rtoax@...mail.com>, vbabka@...e.cz
Cc:     42.hyeyoo@...il.com, akpm@...ux-foundation.org, cl@...ux.com,
        iamjoonsoo.kim@....com, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, penberg@...nel.org, rientjes@...gle.com,
        roman.gushchin@...ux.dev, rongtao@...tc.cn, sdf@...gle.com,
        yhs@...com
Subject: Re: [PATCH] mm: Functions used internally should not be put into



On 1/17/23 11:23 PM, Rong Tao wrote:
> Hi, Vlastimil.
> 
> Thank you for your reply. Indeed, BTF can eliminate the existing problem
> of data structure parsing. But as far as the current BCC[0] code is
> concerned, more surgery may be required.
> 
> Now the bcc problem[1] should probably be solved by the bcc itself using
> BTF, and should not bother the kernel. I hope the maintenance engineers
> at BCC can agree with this. Thanks again.
> 
> [0] https://github.com/iovisor/bcc
> [1] https://github.com/iovisor/bcc/issues/4438

Rong, I have added a comment in above [1]. Let us try to resolve
this issue inside the bcc. Thanks!

> 
> Best wishes.
> 
> Rong Tao