linux-kernel - Re: [PATCH v2 1/4] kernfs: kvmalloc xattr value instead of kmalloc

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: <84ef5548ee27e7150d0b7a5702ce50536cea975a.camel@perches.com>
Date:   Mon, 09 Mar 2020 12:58:49 -0700
From:   Joe Perches <joe@...ches.com>
To:     Tejun Heo <tj@...nel.org>
Cc:     Daniel Xu <dxu@...uu.xyz>, cgroups@...r.kernel.org,
        lizefan@...wei.com, hannes@...xchg.org, shakeelb@...gle.com,
        linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org,
        kernel-team@...com
Subject: Re: [PATCH v2 1/4] kernfs: kvmalloc xattr value instead of kmalloc

On Mon, 2020-03-09 at 15:51 -0400, Tejun Heo wrote:
> On Mon, Mar 09, 2020 at 12:41:05PM -0700, Joe Perches wrote:
> > If the need is to allocate from a single block of memory,
> > perhaps you need a submemory allocator like gen_pool.
> > (gennalloc.h)
> > 
> > Dunno.  Maybe i just don't quite understand your need.
> 
> vmalloc is the right thing to do here. vmalloc space isn't a scarce
> resource on any 64bit machines. On 32bits, which basically are tiny
> machines at this point, these allocations are both size and quantity
> limited by other factors (e.g. each cgroup consumes way more memory).

This feels like driving spikes into a living thing
more than into a
corpse.

I've still got more than a few 32-bit devices around.