linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Rong Tao <rtoax@foxmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Kees Cook <keescook@chromium.org>,
	Florent Revest <revest@chromium.org>,
	David Hildenbrand <david@redhat.com>,
	Josh Triplett <josh@joshtriplett.org>,
	Andy Chiu <andy.chiu@sifive.com>, Joey Gouly <joey.gouly@arm.com>,
	Stefan Roesch <shr@devkernel.io>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Ondrej Mosnacek <omosnace@redhat.com>,
	Miguel Ojeda <ojeda@kernel.org>,
	"open list:MEMORY MANAGEMENT" <linux-mm@kvack.org>,
	open list <linux-kernel@vger.kernel.org>,
	rongtao@cestc.cn
Subject: Re: [PATCH v2] prctl: Get private anonymous memory region name
Date: Sun, 26 Nov 2023 14:56:44 +0100	[thread overview]
Message-ID: <20231126135644.GA7199@redhat.com> (raw)
In-Reply-To: <tencent_77E0BC1E8E9A21CA1B9009DD66555C72A90A@qq.com>

On 11/26, Rong Tao wrote:
>
> then the PR_GET_VMA interface should be provided accordingly,
> which is necessary, as the userspace program usually wants to know what
> VMA name it has configured for the anonymous page.

I don't really understand the use-case for PR_GET_VMA ...

But the patch looks reasonable and correct to me.

Reviewed-by: Oleg Nesterov <oleg@redhat.com>



  reply	other threads:[~2023-11-26 13:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-26  2:56 [PATCH v2] prctl: Get private anonymous memory region name Rong Tao
2023-11-26 13:56 ` Oleg Nesterov [this message]
2023-11-27 14:52   ` David Hildenbrand
2023-11-28  1:02     ` Rong Tao

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=20231126135644.GA7199@redhat.com \
    --to=oleg@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=andy.chiu@sifive.com \
    --cc=catalin.marinas@arm.com \
    --cc=david@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joey.gouly@arm.com \
    --cc=josh@joshtriplett.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ojeda@kernel.org \
    --cc=omosnace@redhat.com \
    --cc=revest@chromium.org \
    --cc=rongtao@cestc.cn \
    --cc=rtoax@foxmail.com \
    --cc=shr@devkernel.io \
    /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;
as well as URLs for NNTP newsgroup(s).