linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: Hugh Dickins <hughd@google.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Pasha Tatashin <pasha.tatashin@soleen.com>,
	Mike Rapoport <rppt@kernel.org>,
	Pratyush Yadav <pratyush@kernel.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] mm: memfd_luo hotfixes
Date: Thu, 22 Jan 2026 16:18:38 +0100	[thread overview]
Message-ID: <20260122151842.4069702-1-pratyush@kernel.org> (raw)

From: "Pratyush Yadav (Google)" <pratyush@kernel.org>

Hi,

This series contains a couple of fixes for memfd preservation using LUO.
Patch 1 is a preparatory patch for patch 2. Patch 2 sets up the right
flags on the file and makes sure security hooks are called. Patch 3
fixes a small memory leak in the error path.

Andrew, it would be great if we can land these in v6.19, especially
patches 1 and 2 since they fix a usability and a security problem. Patch
3 can wait, but then it is pretty simple too. Anyway, since it is pretty
late in the cycle, I'll leave it to your judgement.

Regards,
Pratyush Yadav

Pratyush Yadav (Google) (3):
  memfd: export alloc_file()
  mm: memfd_luo: use memfd_alloc_file() instead of shmem_file_setup()
  mm: memfd_luo: restore and free memfd_luo_ser on failure

 include/linux/memfd.h |  6 ++++++
 mm/memfd.c            |  4 ++--
 mm/memfd_luo.c        | 10 ++++++----
 3 files changed, 14 insertions(+), 6 deletions(-)


base-commit: 1ac8a55c76e78fc4fc406fd7bd872d0127d04feb
-- 
2.52.0.457.g6b5491de43-goog



             reply	other threads:[~2026-01-22 15:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22 15:18 Pratyush Yadav [this message]
2026-01-22 15:18 ` [PATCH 1/3] memfd: export alloc_file() Pratyush Yadav
2026-01-22 15:44   ` Mike Rapoport
2026-01-22 18:00   ` Pasha Tatashin
2026-01-22 15:18 ` [PATCH 2/3] mm: memfd_luo: use memfd_alloc_file() instead of shmem_file_setup() Pratyush Yadav
2026-01-22 15:45   ` Mike Rapoport
2026-01-22 18:01   ` Pasha Tatashin
2026-01-22 15:18 ` [PATCH 3/3] mm: memfd_luo: restore and free memfd_luo_ser on failure Pratyush Yadav
2026-01-22 15:46   ` Mike Rapoport
2026-01-22 18:03   ` Pasha Tatashin
2026-01-22 15:31 ` [PATCH 0/3] mm: memfd_luo hotfixes Andrew Morton

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=20260122151842.4069702-1-pratyush@kernel.org \
    --to=pratyush@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pasha.tatashin@soleen.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