Re: [PATCH] proc: use kmalloc instead of __get_free_page() to alloc path buffer

From: Torin Carey
Date: Tue Jan 25 2022 - 09:14:02 EST


On Sun, Jan 23, 2022 at 10:08:37AM +0000, Hao Lee wrote:
> It's not a standard approach that use __get_free_page() to alloc path
> buffer directly. We'd better use kmalloc and PATH_MAX.

If we're allocating PATH_MAX sized buffers for names, wouldn't it be
suitable to use the name slab names_cachep declared in
include/linux/fs.h using __getname() and __putname()?

Best,
Torin