From: Matthew Wilcox <willy@infradead.org>
To: Kameron Carr <kameroncarr@linux.microsoft.com>
Cc: akpm@linux-foundation.org, urezki@gmail.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, rppt@kernel.org,
catalin.marinas@arm.com, mhklinux@outlook.com
Subject: Re: [RFC PATCH] mm/vmalloc: add vmalloc_decrypted() and vzalloc_decrypted()
Date: Fri, 22 May 2026 04:14:32 +0100 [thread overview]
Message-ID: <ag_KGA4ej9isaQfx@casper.infradead.org> (raw)
In-Reply-To: <20260521205834.1012925-1-kameroncarr@linux.microsoft.com>
On Thu, May 21, 2026 at 01:58:34PM -0700, Kameron Carr wrote:
> +/*
> + * Transition a single contiguous block of @nr pages at index @idx in
There's no parameter called @nr_pages; you probably meant @nr.
> + * @area->pages to encrypted or decrypted state. On failure, the block's
> + * page-pointer slots are cleared so the standard free path will not return
> + * the pages to the allocator (they are leaked).
> + */
> +static int __vm_pages_enc_dec(struct vm_struct *area, unsigned int idx,
> + unsigned int nr, bool encrypt)
This 'bool encrypt' parameter is an antipattern. Just split this into
two functions.
> +{
> + unsigned long addr =
> + (unsigned long)kasan_reset_tag(page_address(area->pages[idx]));
> + int err = encrypt ? set_memory_encrypted(addr, nr) :
> + set_memory_decrypted(addr, nr);
> +
> + if (err)
> + memset(&area->pages[idx], 0, nr * sizeof(*area->pages));
> + return err;
> +}
Does it really make sense to pass in 'area' and 'idx' rather than
passing in &area->pages[idx]?
next prev parent reply other threads:[~2026-05-22 3:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 20:58 [RFC PATCH] mm/vmalloc: add vmalloc_decrypted() and vzalloc_decrypted() Kameron Carr
2026-05-22 3:14 ` Matthew Wilcox [this message]
2026-06-08 15:37 ` Catalin Marinas
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=ag_KGA4ej9isaQfx@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=kameroncarr@linux.microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhklinux@outlook.com \
--cc=rppt@kernel.org \
--cc=urezki@gmail.com \
/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