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@xxxxxxxxxxxxx> > >> --- > >> 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@xxxxxxxxxxxxxxx > > 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:
signature.asc
Description: PGP signature
