MAINTAINERS: Add myself as userfaultfd reviewer
PATCH 1/1 MAINTAINERS: Add myself as userfaultfd reviewer
Add an entry for userfaultfd and make myself a reviewer of it, just in case it helps people manage the cc list.
I named it MEMORY USERFAULTFD, could be a bad name, but then it can be together with the MEMORY* entries when everything is in alphabetic order, which is definitely a benefit.
The line may not change much on how I'd work with userfaultfd; I think I'll do the same as before.. But maybe it still, more or less, adds some responsibility on top, indeed.
--- MAINTAINERS | 11 +++++++++++ 1 file changed, 11 insertions(+)
MAINTAINERS +11 -0
@@ -15220,6 +15220,17 @@ F: mm/vma.h F: mm/vma_internal.h F: tools/testing/vma/ +MEMORY USERFAULTFD +M: Andrew Morton <[email protected]> +R: Peter Xu <[email protected]> +S: Maintained +F: mm/userfaultfd.c +F: fs/userfaultfd.c +F: include/uapi/linux/userfaultfd.h +F: include/asm-generic/pgtable_uffd.h +F: Documentation/admin-guide/mm/userfaultfd.rst +F: tools/testing/selftests/mm/uffd-*.[ch] + MEMORY TECHNOLOGY DEVICES (MTD) M: Miquel Raynal <[email protected]> M: Richard Weinberger <[email protected]>
Signature · 1 line
2.48.1
Andrew Morton
maintainerQuoted 10 lines · On Fri, 21 Mar 2025 20:21:24 -0400 Peter Xu <[email protected]> wrote:
Add an entry for userfaultfd and make myself a reviewer of it, just in case it helps people manage the cc list.
I named it MEMORY USERFAULTFD, could be a bad name, but then it can be together with the MEMORY* entries when everything is in alphabetic order, which is definitely a benefit.
The line may not change much on how I'd work with userfaultfd; I think I'll do the same as before.. But maybe it still, more or less, adds some responsibility on top, indeed.
Thanks. If anyone else would like a cc on userfaultfd emails, please lmk or send a patch.
Hi Peter,
Quoted 23 lines · Peter Xu
Add an entry for userfaultfd and make myself a reviewer of it, just in case it helps people manage the cc list.
I named it MEMORY USERFAULTFD, could be a bad name, but then it can be together with the MEMORY* entries when everything is in alphabetic order, which is definitely a benefit.
The line may not change much on how I'd work with userfaultfd; I think I'll do the same as before.. But maybe it still, more or less, adds some responsibility on top, indeed.
Cc Andrea Arcangeli <[email protected]>Suggested-by Andrew Morton <[email protected]>Signed-off-by Peter Xu <[email protected]>--- MAINTAINERS | 11 +++++++++++ 1 file changed, 11 insertions(+)MAINTAINERS +0
-0
MAINTAINERS F: mm/vma.h · line 15229
Quoted 10 lines
MAINTAINERS +7
-0@@ -15220,6 +15220,17 @@ F: mm/vma.h F: mm/vma_internal.h F: tools/testing/vma/ +MEMORY USERFAULTFD +M: Andrew Morton <[email protected]> +R: Peter Xu <[email protected]> +S: Maintained +F: mm/userfaultfd.c +F: fs/userfaultfd.c +F: include/uapi/linux/userfaultfd.h
There's also
F: include/linux/userfaultfd_k.h
Quoted 10 lines
MAINTAINERS +4
-0+F: include/asm-generic/pgtable_uffd.h +F: Documentation/admin-guide/mm/userfaultfd.rst +F: tools/testing/selftests/mm/uffd-*.[ch] + MEMORY TECHNOLOGY DEVICES (MTD) M: Miquel Raynal <[email protected]> M: Richard Weinberger <[email protected]>Signature · 1 line
2.48.1
Signature · 2 lines
Sincerely yours, Mike.
Quoted 7 lines · Peter Xu
Add an entry for userfaultfd and make myself a reviewer of it, just in case it helps people manage the cc list.
I named it MEMORY USERFAULTFD, could be a bad name, but then it can be together with the MEMORY* entries when everything is in alphabetic order, which is definitely a benefit.
Quoted 7 lines
The line may not change much on how I'd work with userfaultfd; I think I'll do the same as before.. But maybe it still, more or less, adds some responsibility on top, indeed.
Cc Andrea Arcangeli <[email protected]>Suggested-by Andrew Morton <[email protected]>Signed-off-by Peter Xu <[email protected]>
Thanks Peter.
Quoted 29 lines
--- MAINTAINERS | 11 +++++++++++ 1 file changed, 11 insertions(+)MAINTAINERS +11
-0@@ -15220,6 +15220,17 @@ F: mm/vma.h F: mm/vma_internal.h F: tools/testing/vma/ +MEMORY USERFAULTFD +M: Andrew Morton <[email protected]> +R: Peter Xu <[email protected]> +S: Maintained +F: mm/userfaultfd.c +F: fs/userfaultfd.c +F: include/uapi/linux/userfaultfd.h +F: include/asm-generic/pgtable_uffd.h +F: Documentation/admin-guide/mm/userfaultfd.rst +F: tools/testing/selftests/mm/uffd-*.[ch] + MEMORY TECHNOLOGY DEVICES (MTD) M: Miquel Raynal <[email protected]> M: Richard Weinberger <[email protected]>Signature · 1 line
2.48.1
Quoted 7 lines · Peter Xu
Add an entry for userfaultfd and make myself a reviewer of it, just in case it helps people manage the cc list.
I named it MEMORY USERFAULTFD, could be a bad name, but then it can be together with the MEMORY* entries when everything is in alphabetic order, which is definitely a benefit.
Quoted 7 lines
The line may not change much on how I'd work with userfaultfd; I think I'll do the same as before.. But maybe it still, more or less, adds some responsibility on top, indeed.
Cc Andrea Arcangeli <[email protected]>Suggested-by Andrew Morton <[email protected]>Signed-off-by Peter Xu <[email protected]>
Cheers! beers_owed++ ;)
As Mike points out, also needs include/linux/userfaultfd_k.h but Andrew - I guess you can tack that on here?
Quoted 29 lines
--- MAINTAINERS | 11 +++++++++++ 1 file changed, 11 insertions(+)MAINTAINERS +11
-1@@ -15220,6 +15220,17 @@ F: mm/vma.h F: mm/vma_internal.h F: tools/testing/vma/ +MEMORY USERFAULTFD +M: Andrew Morton <[email protected]> +R: Peter Xu <[email protected]> +S: Maintained +F: mm/userfaultfd.c +F: fs/userfaultfd.c +F: include/uapi/linux/userfaultfd.h +F: include/asm-generic/pgtable_uffd.h +F: Documentation/admin-guide/mm/userfaultfd.rst +F: tools/testing/selftests/mm/uffd-*.[ch] + MEMORY TECHNOLOGY DEVICES (MTD) M: Miquel Raynal <[email protected]> M: Richard Weinberger <[email protected]> --2.48.1