public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: linux-kselftest@vger.kernel.org,  rppt@kernel.org,
	 shuah@kernel.org, akpm@linux-foundation.org,
	 linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	 dmatlack@google.com,  pratyush@kernel.org, skhawaja@google.com
Subject: Re: [PATCH v4 2/3] memfd: implement get_id for memfd_luo
Date: Fri, 03 Apr 2026 18:32:03 +0000	[thread overview]
Message-ID: <2vxzpl4fc2u4.fsf@kernel.org> (raw)
In-Reply-To: <20260326163943.574070-3-pasha.tatashin@soleen.com> (Pasha Tatashin's message of "Thu, 26 Mar 2026 16:39:42 +0000")

On Thu, Mar 26 2026, Pasha Tatashin wrote:

> Memfds are identified by their underlying inode. Implement get_id
> for memfd_luo to return the inode pointer. This prevents the same
> memfd from being managed twice by LUO if the same inode is pointed
> by multiple file objects.
>
> Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>

Reviewed-by: Pratyush Yadav (Google) <pratyush@kernel.org>

[...]

-- 
Regards,
Pratyush Yadav

  reply	other threads:[~2026-04-03 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 16:39 [PATCH v4 0/3] liveupdate: prevent double preservation Pasha Tatashin
2026-03-26 16:39 ` [PATCH v4 1/3] liveupdate: prevent double management of files Pasha Tatashin
2026-03-26 16:39 ` [PATCH v4 2/3] memfd: implement get_id for memfd_luo Pasha Tatashin
2026-04-03 18:32   ` Pratyush Yadav [this message]
2026-03-26 16:39 ` [PATCH v4 3/3] selftests: liveupdate: add test for double preservation Pasha Tatashin

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=2vxzpl4fc2u4.fsf@kernel.org \
    --to=pratyush@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=dmatlack@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=rppt@kernel.org \
    --cc=shuah@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