linux-kernel - Re: [PATCH v2] mm: cma: support sysfs

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: <2abc0258-d71a-56f2-3682-cc178f3ce4c4@nvidia.com>
Date:   Tue, 9 Feb 2021 23:50:43 -0800
From:   John Hubbard <jhubbard@...dia.com>
To:     Greg KH <gregkh@...uxfoundation.org>
CC:     Minchan Kim <minchan@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        linux-mm <linux-mm@...ck.org>,
        LKML <linux-kernel@...r.kernel.org>, <surenb@...gle.com>,
        <joaodias@...gle.com>, <willy@...radead.org>
Subject: Re: [PATCH v2] mm: cma: support sysfs

On 2/9/21 11:26 PM, Greg KH wrote:
...
>> I just am not especially happy about the inability to do natural, efficient
>> things here, such as use a statically allocated set of things with sysfs. And
>> I remain convinced that the above is not "improper"; it's a reasonable
>> step, given the limitations of the current sysfs design. I just wanted to say
>> that out loud, as my proposal sinks to the bottom of the trench here. haha :)
> 
> What is "odd" is that you are creating an object in the kernel that you
> _never_ free.  That's not normal at all in the kernel, and so, your wish
> to have a kobject that you never free represent this object also is not
> normal :)
> 

OK, thanks for taking the time to explain that, much appreciated!


thanks,
-- 
John Hubbard
NVIDIA