linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: Alexander Graf <graf@amazon.com>,
	Pasha Tatashin <pasha.tatashin@soleen.com>,
	Hugh Dickins <hughd@google.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jason Gunthorpe <jgg@nvidia.com>,
	Samiullah Khawaja <skhawaja@google.com>,
	kexec@lists.infradead.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] memfd: export memfd_{add,get}_seals()
Date: Sun, 25 Jan 2026 13:52:01 +0200	[thread overview]
Message-ID: <aXYD4b46LcwSodjX@kernel.org> (raw)
In-Reply-To: <20260123095854.535058-2-pratyush@kernel.org>

On Fri, Jan 23, 2026 at 10:58:50AM +0100, Pratyush Yadav wrote:
> From: "Pratyush Yadav (Google)" <pratyush@kernel.org>
> 
> Support for preserving file seals will be added to memfd preservation
> using the Live Update Orchestrator (LUO). Export
> memfd_{add,get}_seals)() so memfd_luo can use them to manipulate the
> seals.
> 
> Signed-off-by: Pratyush Yadav (Google) <pratyush@kernel.org>

Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>

> ---
>  include/linux/memfd.h | 12 ++++++++++++
>  mm/memfd.c            |  4 ++--
>  2 files changed, 14 insertions(+), 2 deletions(-)
> 
> diff --git a/include/linux/memfd.h b/include/linux/memfd.h
> index c328a7b356d0..b4fda09dab9f 100644
> --- a/include/linux/memfd.h
> +++ b/include/linux/memfd.h
> @@ -18,6 +18,8 @@ struct folio *memfd_alloc_folio(struct file *memfd, pgoff_t idx);
>   */
>  int memfd_check_seals_mmap(struct file *file, vm_flags_t *vm_flags_ptr);
>  struct file *memfd_alloc_file(const char *name, unsigned int flags);
> +int memfd_get_seals(struct file *file);
> +int memfd_add_seals(struct file *file, unsigned int seals);
>  #else
>  static inline long memfd_fcntl(struct file *f, unsigned int c, unsigned int a)
>  {
> @@ -37,6 +39,16 @@ static inline struct file *memfd_alloc_file(const char *name, unsigned int flags
>  {
>  	return ERR_PTR(-EINVAL);
>  }
> +
> +static inline int memfd_get_seals(struct file *file)
> +{
> +	return -EINVAL;
> +}
> +
> +static inline int memfd_add_seals(struct file *file, unsigned int seals)
> +{
> +	return -EINVAL;
> +}
>  #endif
>  
>  #endif /* __LINUX_MEMFD_H */
> diff --git a/mm/memfd.c b/mm/memfd.c
> index f032c6052926..46c5508beea4 100644
> --- a/mm/memfd.c
> +++ b/mm/memfd.c
> @@ -228,7 +228,7 @@ static unsigned int *memfd_file_seals_ptr(struct file *file)
>  		     F_SEAL_WRITE | \
>  		     F_SEAL_FUTURE_WRITE)
>  
> -static int memfd_add_seals(struct file *file, unsigned int seals)
> +int memfd_add_seals(struct file *file, unsigned int seals)
>  {
>  	struct inode *inode = file_inode(file);
>  	unsigned int *file_seals;
> @@ -310,7 +310,7 @@ static int memfd_add_seals(struct file *file, unsigned int seals)
>  	return error;
>  }
>  
> -static int memfd_get_seals(struct file *file)
> +int memfd_get_seals(struct file *file)
>  {
>  	unsigned int *seals = memfd_file_seals_ptr(file);
>  
> -- 
> 2.52.0.457.g6b5491de43-goog
> 

-- 
Sincerely yours,
Mike.


  reply	other threads:[~2026-01-25 11:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23  9:58 [PATCH 0/2] mm: memfd_luo: preserve file seals Pratyush Yadav
2026-01-23  9:58 ` [PATCH 1/2] memfd: export memfd_{add,get}_seals() Pratyush Yadav
2026-01-25 11:52   ` Mike Rapoport [this message]
2026-01-23  9:58 ` [PATCH 2/2] mm: memfd_luo: preserve file seals Pratyush Yadav
2026-01-25 12:03   ` Mike Rapoport
2026-01-26 12:47     ` Pratyush Yadav
2026-01-26 14:37       ` Mike Rapoport
2026-02-10 13:15         ` Pratyush Yadav
2026-01-26 18:31     ` Jason Gunthorpe
2026-02-10 13:10       ` Pratyush Yadav
2026-02-10 13:13         ` Jason Gunthorpe
2026-02-10 13:53           ` Pratyush Yadav

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=aXYD4b46LcwSodjX@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=graf@amazon.com \
    --cc=hughd@google.com \
    --cc=jgg@nvidia.com \
    --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=skhawaja@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