[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b2f4c084-47dc-4e92-a9e3-daec3f48425d@redhat.com>
Date: Mon, 27 Nov 2023 15:52:42 +0100
From: David Hildenbrand <david@...hat.com>
To: Oleg Nesterov <oleg@...hat.com>, Rong Tao <rtoax@...mail.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Catalin Marinas <catalin.marinas@....com>,
Kees Cook <keescook@...omium.org>,
Florent Revest <revest@...omium.org>,
Josh Triplett <josh@...htriplett.org>,
Andy Chiu <andy.chiu@...ive.com>,
Joey Gouly <joey.gouly@....com>,
Stefan Roesch <shr@...kernel.io>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Ondrej Mosnacek <omosnace@...hat.com>,
Miguel Ojeda <ojeda@...nel.org>,
"open list:MEMORY MANAGEMENT" <linux-mm@...ck.org>,
open list <linux-kernel@...r.kernel.org>, rongtao@...tc.cn
Subject: Re: [PATCH v2] prctl: Get private anonymous memory region name
On 26.11.23 14:56, Oleg Nesterov wrote:
> 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 ...
>
Can't we simply read "/proc/PID/maps" and just have that information
from there?
Also, I don't understand the exact use case, that should be clarified --
especially, why the existing way is insufficient.
--
Cheers,
David / dhildenb
Powered by blists - more mailing lists