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] [thread-next>] [day] [month] [year] [list]

Message-ID: <tencent_6BA336883F064B42805919971C2AC6AFF508@qq.com>
Date:   Wed, 18 Jan 2023 15:23:58 +0800
From:   Rong Tao <rtoax@...mail.com>
To:     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, rtoax@...mail.com,
        sdf@...gle.com, yhs@...com
Subject: Re: [PATCH] mm: Functions used internally should not be put into

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

Best wishes.

Rong Tao