From: Catalin Marinas <catalin.marinas@arm.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Szabolcs Nagy <szabolcs.nagy@arm.com>,
adobriyan@gmail.com, linux-arm-kernel@lists.infradead.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: document /proc api for arm64 MTE vm flags
Date: Tue, 1 Dec 2020 19:04:06 +0000 [thread overview]
Message-ID: <20201201190406.GC2502@gaia> (raw)
In-Reply-To: <20201120222413.GA28722@gaia>
Hi Jon,
On Fri, Nov 20, 2020 at 10:24:13PM +0000, Catalin Marinas wrote:
> On Fri, Nov 20, 2020 at 11:00:03AM -0700, Jonathan Corbet wrote:
> > On Fri, 20 Nov 2020 14:44:09 +0000
> > Catalin Marinas <catalin.marinas@arm.com> wrote:
> >
> > > On Fri, Nov 06, 2020 at 10:19:40AM +0000, Szabolcs Nagy wrote:
> > > > Document that /proc/PID/smaps shows PROT_MTE settings in VmFlags.
> > > > Support for this was introduced in
> > > >
> > > > commit 9f3419315f3cdc41a7318e4d50ba18a592b30c8c
> > > > arm64: mte: Add PROT_MTE support to mmap() and mprotect()
> > > >
> > > > Signed-off-by: Szabolcs Nagy <szabolcs.nagy@arm.com>
> > > > Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
> > > > Cc: linux-doc@vger.kernel.org
> > > > ---
> > > > Documentation/filesystems/proc.rst | 1 +
> > > > 1 file changed, 1 insertion(+)
> > > >
> > > > diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
> > > > index 533c79e8d2cd..e5fa972d4c76 100644
> > > > --- a/Documentation/filesystems/proc.rst
> > > > +++ b/Documentation/filesystems/proc.rst
> > > > @@ -546,6 +546,7 @@ encoded manner. The codes are the following:
> > > > nh no huge page advise flag
> > > > mg mergable advise flag
> > > > bt arm64 BTI guarded page
> > > > + mt arm64 MTE allocation tags are enabled
> > > > == =======================================
> > > >
> > > > Note that there is no guarantee that every flag and associated mnemonic will
> > >
> > > Are you ok with picking up this patch (it can be left for 5.11) or
> > > should I queue it in the arm64 tree?
> >
> > It wasn't sent to me, so it wasn't on my radar. Up to you, I'm happy to
> > grab it if you'd prefer.
>
> Please do grab it. Thanks.
In case it slipped through the cracks (I haven't seen it in -next).
Otherwise I'll queue it sometime later this week for 5.11.
Thanks.
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Szabolcs Nagy <szabolcs.nagy@arm.com>,
adobriyan@gmail.com, linux-arm-kernel@lists.infradead.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: document /proc api for arm64 MTE vm flags
Date: Tue, 1 Dec 2020 19:04:06 +0000 [thread overview]
Message-ID: <20201201190406.GC2502@gaia> (raw)
In-Reply-To: <20201120222413.GA28722@gaia>
Hi Jon,
On Fri, Nov 20, 2020 at 10:24:13PM +0000, Catalin Marinas wrote:
> On Fri, Nov 20, 2020 at 11:00:03AM -0700, Jonathan Corbet wrote:
> > On Fri, 20 Nov 2020 14:44:09 +0000
> > Catalin Marinas <catalin.marinas@arm.com> wrote:
> >
> > > On Fri, Nov 06, 2020 at 10:19:40AM +0000, Szabolcs Nagy wrote:
> > > > Document that /proc/PID/smaps shows PROT_MTE settings in VmFlags.
> > > > Support for this was introduced in
> > > >
> > > > commit 9f3419315f3cdc41a7318e4d50ba18a592b30c8c
> > > > arm64: mte: Add PROT_MTE support to mmap() and mprotect()
> > > >
> > > > Signed-off-by: Szabolcs Nagy <szabolcs.nagy@arm.com>
> > > > Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
> > > > Cc: linux-doc@vger.kernel.org
> > > > ---
> > > > Documentation/filesystems/proc.rst | 1 +
> > > > 1 file changed, 1 insertion(+)
> > > >
> > > > diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
> > > > index 533c79e8d2cd..e5fa972d4c76 100644
> > > > --- a/Documentation/filesystems/proc.rst
> > > > +++ b/Documentation/filesystems/proc.rst
> > > > @@ -546,6 +546,7 @@ encoded manner. The codes are the following:
> > > > nh no huge page advise flag
> > > > mg mergable advise flag
> > > > bt arm64 BTI guarded page
> > > > + mt arm64 MTE allocation tags are enabled
> > > > == =======================================
> > > >
> > > > Note that there is no guarantee that every flag and associated mnemonic will
> > >
> > > Are you ok with picking up this patch (it can be left for 5.11) or
> > > should I queue it in the arm64 tree?
> >
> > It wasn't sent to me, so it wasn't on my radar. Up to you, I'm happy to
> > grab it if you'd prefer.
>
> Please do grab it. Thanks.
In case it slipped through the cracks (I haven't seen it in -next).
Otherwise I'll queue it sometime later this week for 5.11.
Thanks.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-12-01 19:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 10:19 [PATCH] Documentation: document /proc api for arm64 MTE vm flags Szabolcs Nagy
2020-11-06 10:19 ` Szabolcs Nagy
2020-11-20 14:44 ` Catalin Marinas
2020-11-20 14:44 ` Catalin Marinas
2020-11-20 18:00 ` Jonathan Corbet
2020-11-20 18:00 ` Jonathan Corbet
2020-11-20 22:24 ` Catalin Marinas
2020-11-20 22:24 ` Catalin Marinas
2020-12-01 19:04 ` Catalin Marinas [this message]
2020-12-01 19:04 ` Catalin Marinas
2020-12-01 19:29 ` Jonathan Corbet
2020-12-01 19:29 ` Jonathan Corbet
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=20201201190406.GC2502@gaia \
--to=catalin.marinas@arm.com \
--cc=adobriyan@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=szabolcs.nagy@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.