The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Tarun Sahu <tarunsahu@google.com>
Cc: Pasha Tatashin <pasha.tatashin@soleen.com>,
	Pratyush Yadav <pratyush@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	kexec@lists.infradead.org
Subject: Re: [PATCH 0/1] mm/memfd_luo: use KHOSER_PTR for serialized_data checks
Date: Tue, 16 Jun 2026 09:44:44 +0300	[thread overview]
Message-ID: <ajDw3DQ13ZpvW__D@kernel.org> (raw)
In-Reply-To: <cover.1781528022.git.tarunsahu@google.com>

Hi,

On Mon, Jun 15, 2026 at 01:05:04PM +0000, Tarun Sahu wrote:
> Use the KHOSER_PTR interface for serialized_data in memfd_luo to
> perform type-safe pointer conversions and checks.
> 
> I have tried to keep the changes minimal. So only changed
> the memfd_luo. Would love the suggestions for if we should be changing
> struct liveupdate_file_op_args like the following.
> 
> @@ -46,7 +47,7 @@ struct liveupdate_file_op_args {
>  	struct liveupdate_file_handler *handler;
>  	int retrieve_status;
>  	struct file *file;
> -	u64 serialized_data;
> +	DECLARE_KHOSER_PTR(serialized_data, void *);

Yes, this one please :)

>  	void *private_data;
>  };
> 
> Ofcourse, it will require change in liveupdate and luo_file.
> 
> Tarun Sahu (1):
>   mm/memfd_luo: use KHOSER_PTR for serialized_data checks
> 
>  mm/memfd_luo.c | 30 +++++++++++++++++++++---------
>  1 file changed, 21 insertions(+), 9 deletions(-)
> 
> 
> base-commit: 0e0611827f3349d0a2ac121c023a6d3260dcecdb
> -- 
> 2.54.0.1136.gdb2ca164c4-goog
> 

-- 
Sincerely yours,
Mike.

      parent reply	other threads:[~2026-06-16  6:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-15 13:05 [PATCH 0/1] mm/memfd_luo: use KHOSER_PTR for serialized_data checks Tarun Sahu
2026-06-15 13:05 ` [PATCH 1/1] " Tarun Sahu
2026-06-16  6:44 ` Mike Rapoport [this message]

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=ajDw3DQ13ZpvW__D@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    --cc=tarunsahu@google.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