From: Alejandro Colomar <alx@kernel.org>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>
Cc: kernel@collabora.com, linux-man@vger.kernel.org
Subject: Re: [PATCH 1/2] ioctl_userfaultfd.2: add UFFD_FEATURE_WP_ASYNC
Date: Thu, 19 Oct 2023 15:42:39 +0200 [thread overview]
Message-ID: <ZTEyT9gbTL5g4pUz@debian> (raw)
In-Reply-To: <041045ed-55e4-44ff-b5a9-cfdf252c33d3@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 1839 bytes --]
Hi Muhammad,
On Thu, Oct 19, 2023 at 06:34:26PM +0500, Muhammad Usama Anjum wrote:
> On 10/19/23 6:29 PM, Alejandro Colomar wrote:
> > On Thu, Oct 19, 2023 at 06:12:44PM +0500, Muhammad Usama Anjum wrote:
> >> Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
> >> ---
> >> Changes since v1:
> >> - Employ sementic new lines by breaking sentence before "by"
> >> ---
> >> man2/ioctl_userfaultfd.2 | 5 +++++
> >> 1 file changed, 5 insertions(+)
> >>
> >> diff --git a/man2/ioctl_userfaultfd.2 b/man2/ioctl_userfaultfd.2
> >> index e68085262..f6cafd9a2 100644
> >> --- a/man2/ioctl_userfaultfd.2
> >> +++ b/man2/ioctl_userfaultfd.2
> >> @@ -244,6 +244,11 @@ If this feature bit is set,
> >> the kernel supports resolving faults with the
> >> .B UFFDIO_POISON
> >> ioctl.
> >> +.TP
> >> +.BR UFFD_FEATURE_WP_ASYNC " (since Linux 6.7)"
> >
> > Has this feature been merged?
> Yes, This patch is in maintainer's tree (in mm-stable these day).
> https://lore.kernel.org/all/20231018213452.A78A8C433C8@smtp.kernel.org
>
> It should be released with next kernel release.
>
> I'm not sure if you can accept a patch which isn't in Linus's tree yet. But
> these patches are already in maintainer's tree and in linux-next from
> almost a month.
Yep, if it's in a maintainer tree, I prefer merging it already, unless
you expect significant changes before Linus. If anything happens, we
can fix it later.
In linux-next, I'd prefer to wait.
Cheers,
Alex
> >
> > Thanks,
> > Alex
> >
> >> +If this feature bit is set,
> >> +the write protection faults would be asynchronously resolved
> >> +by the kernel.
> >> .PP
> >> The returned
> >> .I ioctls
> >> --
> >> 2.42.0
> >>
> >
>
> --
> BR,
> Muhammad Usama Anjum
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-19 13:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 13:12 [PATCH 1/2] ioctl_userfaultfd.2: add UFFD_FEATURE_WP_ASYNC Muhammad Usama Anjum
2023-10-19 13:12 ` [PATCH 2/2] ioctl_pagemap_scan: add page for pagemap_scan IOCTL Muhammad Usama Anjum
2023-10-23 21:52 ` Alejandro Colomar
2023-10-24 2:48 ` G. Branden Robinson
2023-10-24 10:40 ` Alejandro Colomar
2023-10-28 13:07 ` managing tagged paragraphs (was: [PATCH 2/2] ioctl_pagemap_scan: add page for pagemap_scan IOCTL) G. Branden Robinson
2023-10-28 16:22 ` Alejandro Colomar
2023-10-28 18:07 ` G. Branden Robinson
2023-10-29 0:42 ` Alejandro Colomar
2023-10-24 15:51 ` [PATCH 2/2] ioctl_pagemap_scan: add page for pagemap_scan IOCTL Muhammad Usama Anjum
2023-10-19 13:27 ` [PATCH 1/2] ioctl_userfaultfd.2: add UFFD_FEATURE_WP_ASYNC Alejandro Colomar
2023-10-19 13:29 ` Alejandro Colomar
2023-10-19 13:34 ` Muhammad Usama Anjum
2023-10-19 13:42 ` Alejandro Colomar [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-17 15:01 Muhammad Usama Anjum
2023-10-17 16:41 ` Alejandro Colomar
2023-10-19 7:26 ` Muhammad Usama Anjum
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=ZTEyT9gbTL5g4pUz@debian \
--to=alx@kernel.org \
--cc=kernel@collabora.com \
--cc=linux-man@vger.kernel.org \
--cc=usama.anjum@collabora.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