From: David Laight <david.laight.linux@gmail.com>
To: Mahad Ibrahim <mahad.ibrahim.dev@gmail.com>
Cc: Kees Cook <kees@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mike Rapoport <rppt@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lkdtm: use kmalloc() instead of __get_free_page
Date: Thu, 23 Jul 2026 09:45:22 +0100 [thread overview]
Message-ID: <20260723094522.535b284c@pumpkin> (raw)
In-Reply-To: <20260722230246.2869-1-mahad.ibrahim.dev@gmail.com>
On Wed, 22 Jul 2026 23:02:46 +0000
Mahad Ibrahim <mahad.ibrahim.dev@gmail.com> wrote:
> lkdtm_debugfs_entry and direct_entry use __get_free_page to allocate a
> temporary buffer, perform copy_from_user to get the crashtype name,
> strim() to strip whitespace and find_crashtype to find the corresponding
> crashtype that is being requested.
>
> The lkdtm_debugfs_read uses __get_free_page to allocate a temporary
> buffer to store all the available crashtypes, and then copy it to
> userspace.
>
> The buffers that are allocated can be allocated with kmalloc as there is
> nothing special that requires a struct page, or the page allocator.
>
> kmalloc() additionally provides a better API that doesn't require ugly
> casts which obfuscate the code and kfree does not need to know the size
> of the freed object.
>
> Replace use of __get_free_page() with kmalloc().
None of those buffers need to be PAGE_SIZE.
Even the sanity limit for overlong requests could be 4k.
The longest 'crashtype->name' is probably about 32 characters, so could
probably go on stack.
And can't this code use the sysfs/kernfs wrappers?
David
>
> Signed-off-by: Mahad Ibrahim <mahad.ibrahim.dev@gmail.com>
> ---
> drivers/misc/lkdtm/core.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/misc/lkdtm/core.c b/drivers/misc/lkdtm/core.c
> index ededa32d6744..01bebcb33bd4 100644
> --- a/drivers/misc/lkdtm/core.c
> +++ b/drivers/misc/lkdtm/core.c
> @@ -236,11 +236,11 @@ static ssize_t lkdtm_debugfs_entry(struct file *f,
> if (count >= PAGE_SIZE)
> return -EINVAL;
>
> - buf = (char *)__get_free_page(GFP_KERNEL);
> + buf = kmalloc(PAGE_SIZE, GFP_KERNEL);
> if (!buf)
> return -ENOMEM;
> if (copy_from_user(buf, user_buf, count)) {
> - free_page((unsigned long) buf);
> + kfree(buf);
> return -EFAULT;
> }
> /* NULL-terminate and remove enter */
> @@ -248,7 +248,7 @@ static ssize_t lkdtm_debugfs_entry(struct file *f,
> strim(buf);
>
> crashtype = find_crashtype(buf);
> - free_page((unsigned long)buf);
> + kfree(buf);
>
> if (!crashtype)
> return -EINVAL;
> @@ -271,7 +271,7 @@ static ssize_t lkdtm_debugfs_read(struct file *f, char __user *user_buf,
> ssize_t out;
> char *buf;
>
> - buf = (char *)__get_free_page(GFP_KERNEL);
> + buf = kmalloc(PAGE_SIZE, GFP_KERNEL);
> if (buf == NULL)
> return -ENOMEM;
>
> @@ -290,7 +290,7 @@ static ssize_t lkdtm_debugfs_read(struct file *f, char __user *user_buf,
>
> out = simple_read_from_buffer(user_buf, count, off,
> buf, n);
> - free_page((unsigned long) buf);
> + kfree(buf);
>
> return out;
> }
> @@ -313,11 +313,11 @@ static ssize_t direct_entry(struct file *f, const char __user *user_buf,
> if (count < 1)
> return -EINVAL;
>
> - buf = (char *)__get_free_page(GFP_KERNEL);
> + buf = kmalloc(PAGE_SIZE, GFP_KERNEL);
> if (!buf)
> return -ENOMEM;
> if (copy_from_user(buf, user_buf, count)) {
> - free_page((unsigned long) buf);
> + kfree(buf);
> return -EFAULT;
> }
> /* NULL-terminate and remove enter */
> @@ -325,7 +325,7 @@ static ssize_t direct_entry(struct file *f, const char __user *user_buf,
> strim(buf);
>
> crashtype = find_crashtype(buf);
> - free_page((unsigned long) buf);
> + kfree(buf);
> if (!crashtype)
> return -EINVAL;
>
next prev parent reply other threads:[~2026-07-23 8:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 23:02 [PATCH] lkdtm: use kmalloc() instead of __get_free_page Mahad Ibrahim
2026-07-22 23:42 ` Mahad Ibrahim
2026-07-23 3:47 ` Kees Cook
2026-07-23 8:45 ` David Laight [this message]
2026-07-23 9:00 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260723094522.535b284c@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mahad.ibrahim.dev@gmail.com \
--cc=rppt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox