Linux API

• Thread Index

• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Davidlohr Bueso <dave@xxxxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [RFC PATCH v2] userfaultfd: Add feature to request for a signal delivery
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH] userfaultfd: Add feature to request for a signal delivery
  • From: Andrea Arcangeli <aarcange@xxxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 1/8] signal/alpha: Document a conflict with SI_USER for SIGTRAP
  • From: Helge Deller <deller@xxxxxx>
• Re: [RFC PATCH] userfaultfd: Add feature to request for a signal delivery
  • From: prakash sangappa <prakash.sangappa@xxxxxxxxxx>
• Re: [PATCH 3/8] signal/sparc: Document a conflict with SI_USER with SIGFPE
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Krister Johansen <kjlx@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 3/8] signal/sparc: Document a conflict with SI_USER with SIGFPE
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [RFC PATCH] userfaultfd: Add feature to request for a signal delivery
  • From: Andrea Arcangeli <aarcange@xxxxxxxxxx>
• [PATCH 3/8] signal/sparc: Document a conflict with SI_USER with SIGFPE
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 5/8] signal/testing: Don't look for __SI_FAULT in userspace
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 8/8] signal: Remove kernel interal si_code magic
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 7/8] fcntl: Don't use ambiguous SIG_POLL si_codes
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 6/8] signal/x86: Fix SIGSYS handling in copy_siginfo_to_user32
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 4/8] signal/mips: Document a conflict with SI_USER with SIGFPE
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 2/8] signal/ia64: Document a conflict with SI_USER with SIGFPE
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 1/8] signal/alpha: Document a conflict with SI_USER for SIGTRAP
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 0/8] signal: Fix sending signals with siginfo
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Marcelo Tosatti <mtosatti@xxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Marcelo Tosatti <mtosatti@xxxxxxxxxx>
• Re: [RFC PATCH] userfaultfd: Add feature to request for a signal delivery
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Marcelo Tosatti <mtosatti@xxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Jakub Kicinski <jakub.kicinski@xxxxxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Jakub Kicinski <jakub.kicinski@xxxxxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [RFC PATCH] userfaultfd: Add feature to request for a signal delivery
  • From: "prakash.sangappa" <prakash.sangappa@xxxxxxxxxx>
• Re: [RFC PATCH] userfaultfd: Add feature to request for a signal delivery
  • From: "prakash.sangappa" <prakash.sangappa@xxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Jakub Kicinski <jakub.kicinski@xxxxxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Davidlohr Bueso <dave@xxxxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Davidlohr Bueso <dave@xxxxxxxxxxxx>
• Re: [PATCH 0/4] firmware: fix fallback mechanism by ignoring SIGCHLD
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• RE: [PATCH 2/4] swait: add the missing killable swaits
  • From: Matthew Wilcox <mawilcox@xxxxxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH net-next v3 02/13] sock: skb_copy_ubufs support for compound pages
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• Re: [PATCH 0/4] firmware: fix fallback mechanism by ignoring SIGCHLD
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH 2/4] swait: add the missing killable swaits
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH] userfaultfd: Add feature to request for a signal delivery
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH] userfaultfd: Add feature to request for a signal delivery
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [RFC PATCH] userfaultfd: Add feature to request for a signal delivery
  • From: Prakash Sangappa <prakash.sangappa@xxxxxxxxxx>
• Re: [PATCH v10 1/3] x86/syscalls: Check address limit on user-mode return
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH 0/3] Enable namespaced file capabilities
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [RFC PATCH] userfaultfd: Add feature to request for a signal delivery
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH] userfaultfd: Add feature to request for a signal delivery
  • From: Prakash Sangappa <prakash.sangappa@xxxxxxxxxx>
• Re: [PATCH net-next v3 02/13] sock: skb_copy_ubufs support for compound pages
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• Re: [PATCH v2 07/22] fpga: intel: pcie: parse feature list and create platform device for features.
  • From: Alan Tull <atull@xxxxxxxxxx>
• Re: [PATCH v2 07/22] fpga: intel: pcie: parse feature list and create platform device for features.
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• Re: [PATCH 0/4] firmware: fix fallback mechanism by ignoring SIGCHLD
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH v2 07/22] fpga: intel: pcie: parse feature list and create platform device for features.
  • From: Moritz Fischer <mdf@xxxxxxxxxx>
• Re: [PATCH 1/9] fs: add fcntl() interface for setting/getting write life time hints
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/9] fs: add fcntl() interface for setting/getting write life time hints
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH 1/9] fs: add fcntl() interface for setting/getting write life time hints
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/9] fs: add fcntl() interface for setting/getting write life time hints
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH v2 04/22] fpga: mgr: add region_id to fpga_image_info
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 07/22] fpga: intel: pcie: parse feature list and create platform device for features.
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 06/22] fpga: intel: add FPGA PCIe device driver
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 08/22] fpga: intel: pcie: add chardev support for feature devices
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 05/22] fpga: mgr: add status for fpga-mgr
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 10/22] fpga: intel: add feature device infrastructure
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 14/22] fpga: intel: fme: add partial reconfiguration sub feature support
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 11/22] fpga: intel: add FPGA Management Engine driver basic framework
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 15/22] fpga: intel: add fpga manager platform driver for FME
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 13/22] fpga: intel: fme: add FPGA_GET_API_VERSION/CHECK_EXTENSION ioctls support
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 19/22] fpga: intel: afu: add header sub feature support
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 17/22] fpga: intel: add fpga region platform driver for FME
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 20/22] fpga: intel: afu add FPGA_GET_API_VERSION/CHECK_EXTENSION ioctls support
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 22/22] fpga: intel: afu: add FPGA_PORT_DMA_MAP/UNMAP ioctls support
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 21/22] fpga: intel: afu: add user afu sub feature support
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 18/22] fpga: intel: add FPGA Accelerated Function Unit driver basic framework
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 16/22] fpga: intel: add fpga bridge platform driver for FME
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 12/22] fpga: intel: fme: add header sub feature support
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 09/22] fpga: intel: pcie: adds fpga_for_each_port callback for fme device
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 03/22] fpga: bridge: remove OF dependency for fpga-bridge
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 02/22] fpga: add FPGA device framework
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 01/22] docs: fpga: add a document for Intel FPGA driver overview
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• [PATCH v2 00/22] Intel FPGA Device Drivers
  • From: Wu Hao <hao.wu@xxxxxxxxx>
• Re: [PATCH net-next v3 02/13] sock: skb_copy_ubufs support for compound pages
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH net-next v3 02/13] sock: skb_copy_ubufs support for compound pages
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH net-next v3 02/13] sock: skb_copy_ubufs support for compound pages
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• Re: [PATCH net-next v3 06/13] sock: MSG_ZEROCOPY notification coalescing
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH net-next v3 03/13] sock: add MSG_ZEROCOPY
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH net-next v3 02/13] sock: skb_copy_ubufs support for compound pages
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH net-next v3 03/13] sock: add MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v3 01/13] sock: allocate skbs from optmem
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v3 04/13] sock: add SOCK_ZEROCOPY sockopt
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v3 06/13] sock: MSG_ZEROCOPY notification coalescing
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v3 07/13] sock: add ee_code SO_EE_CODE_ZEROCOPY_COPIED
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v3 10/13] udp: enable MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v3 09/13] tcp: enable MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v3 08/13] sock: ulimit on MSG_ZEROCOPY pages
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v3 05/13] sock: enable MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v3 12/13] packet: enable MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v3 11/13] raw: enable MSG_ZEROCOPY with IP_HDRINCL
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v3 13/13] test: add msg_zerocopy test
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v3 02/13] sock: skb_copy_ubufs support for compound pages
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v3 00/13] socket sendmsg MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• Re: [PATCH net-next v2 04/13] sock: add SOCK_ZEROCOPY sockopt
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v2 00/13] socket sendmsg MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v2 04/13] sock: add SOCK_ZEROCOPY sockopt
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v2 03/13] sock: add MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v2 05/13] sock: enable MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v2 02/13] sock: skb_copy_ubufs support for compound pages
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v2 01/13] sock: allocate skbs from optmem
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v2 09/13] tcp: enable MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v2 08/13] sock: ulimit on MSG_ZEROCOPY pages
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v2 07/13] sock: add ee_code SO_EE_CODE_ZEROCOPY_COPIED
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v2 11/13] raw: enable MSG_ZEROCOPY with IP_HDRINCL
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v2 12/13] packet: enable MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v2 13/13] test: add msg_zerocopy test
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v2 10/13] udp: enable MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next v2 06/13] sock: MSG_ZEROCOPY notification coalescing
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• Re: [PATCH v10 3/3] arm64/syscalls: Check address limit on user-mode return
  • From: Thomas Garnier <thgarnie@xxxxxxxxxx>
• Re: [PATCH v10 2/3] arm/syscalls: Check address limit on user-mode return
  • From: Will Deacon <will.deacon@xxxxxxx>
• Re: [PATCH v10 3/3] arm64/syscalls: Check address limit on user-mode return
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v10 2/3] arm/syscalls: Check address limit on user-mode return
  • From: Thomas Garnier <thgarnie@xxxxxxxxxx>
• Re: [PATCH v10 1/3] x86/syscalls: Check address limit on user-mode return
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v10 2/3] arm/syscalls: Check address limit on user-mode return
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH 1/1] mm: only dispaly online cpus of the numa node
  • From: Zhen Lei <thunder.leizhen@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [RFC PATCH 1/2] mm: introduce bmap_walk()
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [RFC PATCH 1/2] mm: introduce bmap_walk()
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH 1/2] mm: introduce bmap_walk()
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH net-next 02/13] sock: skb_copy_ubufs support for compound pages
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• Re: [PATCH net-next 04/13] sock: add SOCK_ZEROCOPY sockopt and net.core.msg_zerocopy sysctl
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH net-next 02/13] sock: skb_copy_ubufs support for compound pages
  • From: kbuild test robot <lkp@xxxxxxxxx>
• [PATCH net-next 04/13] sock: add SOCK_ZEROCOPY sockopt and net.core.msg_zerocopy sysctl
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next 01/13] sock: allocate skbs from optmem
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next 05/13] sock: enable MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next 08/13] sock: ulimit on MSG_ZEROCOPY pages
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next 09/13] tcp: enable MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next 06/13] sock: MSG_ZEROCOPY notification coalescing
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next 07/13] sock: add ee_code SO_EE_CODE_ZEROCOPY_COPIED
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next 13/13] test: add msg_zerocopy test
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next 03/13] sock: add MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next 12/13] packet: enable MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next 10/13] udp: enable MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next 11/13] raw: enable MSG_ZEROCOPY with IP_HDRINCL
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next 02/13] sock: skb_copy_ubufs support for compound pages
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• [PATCH net-next 00/13] socket sendmsg MSG_ZEROCOPY
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [RFC PATCH 1/2] mm: introduce bmap_walk()
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [RFC PATCH 1/2] mm: introduce bmap_walk()
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 04/10] fs: Introduce RWF_NOWAIT and FMODE_AIO_NOWAIT
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [RFC PATCH 1/2] mm: introduce bmap_walk()
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 04/10] fs: Introduce RWF_NOWAIT and FMODE_AIO_NOWAIT
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [RFC PATCH 1/2] mm: introduce bmap_walk()
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [RFC PATCH 0/2] daxfile: enable byte-addressable updates to pmem
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 0/10 v12] No wait AIO
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 0/10 v12] No wait AIO
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 0/10 v12] No wait AIO
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/10 v12] No wait AIO
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 0/10 v12] No wait AIO
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 02/10] fs: Introduce filemap_range_has_page()
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 07/10] block: return on congested block device
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH 10/10] btrfs: nowait aio support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 08/10] ext4: nowait aio support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 09/10] xfs: nowait aio support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 06/10] fs: Introduce IOMAP_NOWAIT
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 07/10] block: return on congested block device
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 04/10] fs: Introduce RWF_NOWAIT and FMODE_AIO_NOWAIT
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 05/10] fs: return if direct write will trigger writeback
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 03/10] fs: Use RWF_* flags for AIO operations
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 02/10] fs: Introduce filemap_range_has_page()
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 01/10] fs: Separate out kiocb flags setup based on RWF_* flags
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 0/10 v12] No wait AIO
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 0/10 v11] No wait AIO
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 0/10 v11] No wait AIO
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/4] firmware: fix fallback mechanism by ignoring SIGCHLD
  • From: Martin Fuzzey <mfuzzey@xxxxxxxxxxx>
• Re: [Question or BUG] [NUMA]: I feel puzzled at the function cpumask_of_node
  • From: "Leizhen (ThunderTown)" <thunder.leizhen@xxxxxxxxxx>
• [PATCH v10 3/3] arm64/syscalls: Check address limit on user-mode return
  • From: Thomas Garnier <thgarnie@xxxxxxxxxx>
• [PATCH v10 1/3] x86/syscalls: Check address limit on user-mode return
  • From: Thomas Garnier <thgarnie@xxxxxxxxxx>
• [PATCH v10 2/3] arm/syscalls: Check address limit on user-mode return
  • From: Thomas Garnier <thgarnie@xxxxxxxxxx>
• [PATCH 0/4] firmware: fix fallback mechanism by ignoring SIGCHLD
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• [PATCH 1/4] test_firmware: add test case for SIGCHLD on sync fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• [PATCH 3/4] firmware: avoid invalid fallback aborts by using killable swait
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• [PATCH 2/4] swait: add the missing killable swaits
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• [PATCH 4/4] firmware: send -EINTR on signal abort on fallback mechanism
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• [PATCH] xcrypt.3: warn folks not to use these functions
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [patch] mm, vmpressure: pass-through notification support
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH 0/10 v11] No wait AIO
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 0/10 v11] No wait AIO
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 0/10 v11] No wait AIO
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 04/10] fs: Introduce RWF_NOWAIT
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: Martin Fuzzey <mfuzzey@xxxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [Question or BUG] [NUMA]: I feel puzzled at the function cpumask_of_node
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH 0/10 v11] No wait AIO
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: Martin Fuzzey <mfuzzey@xxxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH 00/26] Fixing wait, exit, ptrace, exec, and CLONE_THREAD
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH 06/26] rlimit: Remove unnecessary grab of tasklist_lock
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH 08/26] exit: Make the runqueue rcu safe
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH 06/26] rlimit: Remove unnecessary grab of tasklist_lock
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: Alan Cox <alan@xxxxxxxxxxxxxxx>
• Re: [PATCH 00/26] Fixing wait, exit, ptrace, exec, and CLONE_THREAD
  • From: Aleksa Sarai <asarai@xxxxxxx>
• Re: [PATCH 00/26] Fixing wait, exit, ptrace, exec, and CLONE_THREAD
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH 03/26] signal: Do not perform permission checks when sending pdeath_signal
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 03/26] signal: Do not perform permission checks when sending pdeath_signal
  • From: Richard Weinberger <richard.weinberger@xxxxxxxxx>
• Re: [PATCH 00/26] Fixing wait, exit, ptrace, exec, and CLONE_THREAD
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 03/26] signal: Do not perform permission checks when sending pdeath_signal
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 00/26] Fixing wait, exit, ptrace, exec, and CLONE_THREAD
  • From: Aleksa Sarai <asarai@xxxxxxx>
• [PATCH 26/26] pidns: Ensure zap_pid_ns_processes always terminates
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 25/26] signal: In ptrace_stop use CLD_TRAPPED in all ptrace signals
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 12/26] wait: Directly test for the two cases where wait_task_zombie is called
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 17/26] exit: Rework the exit states for ptracees
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 23/26] signal: Fix SIGCONT before group stop completes.
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 22/26] exit: Fix auto-wait of ptraced children
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 14/26] wait: Move changing of ptrace from wait_consider_task into wait_task_stopped
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 18/26] wait: Fix WSTOPPED on a ptraced child
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 19/26] wait: Simpler code for clearing notask_error in wait_consider_task
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 21/26] wait: Optmize waitpid
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 11/26] wait: Properly implement __WCLONE handling in the presence of exec and ptrace
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 24/26] signal: In ptrace_stop improve identical signal detection
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 15/26] wait: Don't delay !ptrace_reparented leaders
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 20/26] wait: Don't pass the list to wait_consider_task
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 13/26] wait: Remove unused delay_group_leader
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 16/26] exit: Fix reporting a ptraced !reparented leader has exited
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 04/26] signal: Make group_send_sig_info static
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 01/26] alpha: Remove unused TASK_GROUP_LEADER
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 05/26] exit: Remove the pointless clearing of SIGPENDING in __exit_signal
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 09/26] signal: Don't allow sending SIGKILL or SIGSTOP to init
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 07/26] pidns: Improve the error handling in alloc_pid
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 06/26] rlimit: Remove unnecessary grab of tasklist_lock
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 03/26] signal: Do not perform permission checks when sending pdeath_signal
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 08/26] exit: Make the runqueue rcu safe
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 10/26] ptrace: Simplify ptrace_detach & exit_ptrace
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 02/26] cgroup: Don't open code tasklist_empty()
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• [PATCH 00/26] Fixing wait, exit, ptrace, exec, and CLONE_THREAD
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: Alan Cox <alan@xxxxxxxxxxxxxxx>
• [PATCHv7 14/14] x86/mm: Allow to have userspace mappings above 47-bits
  • From: "Kirill A. Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
• [PATCH 03/10] fs: Use RWF_* flags for AIO operations
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 02/10] fs: Introduce filemap_range_has_page()
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 05/10] fs: return if direct write will trigger writeback
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 04/10] fs: Introduce RWF_NOWAIT
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 07/10] block: return on congested block device
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 10/10] btrfs: nowait aio support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 08/10] ext4: nowait aio support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 01/10] fs: Separate out kiocb flags setup based on RWF_* flags
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 09/10] xfs: nowait aio support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 06/10] fs: Introduce IOMAP_NOWAIT
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 0/10 v11] No wait AIO
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: Martin Fuzzey <mfuzzey@xxxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH 07/10] fs: return on congested block device
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] utimensat: immutable flag returns -EPERM
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH] mm: make PR_SET_THP_DISABLE immediately active
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH] mm: make PR_SET_THP_DISABLE immediately active
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx>
• [PATCH 01/10] fs: Separate out kiocb flags setup based on RWF_* flags
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 06/10] fs: Introduce IOMAP_NOWAIT
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 02/10] fs: Introduce filemap_range_has_page()
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 07/10] fs: return on congested block device
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 05/10] fs: return if direct write will trigger writeback
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 04/10] fs: Introduce RWF_NOWAIT
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 03/10] fs: Use RWF_* flags for AIO operations
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 09/10] xfs: nowait aio support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 10/10] btrfs: nowait aio support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 08/10] ext4: nowait aio support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 0/10 v10] No wait AIO
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH] mm: make PR_SET_THP_DISABLE immediately active
  • From: Mike Rapoprt <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mm: make PR_SET_THP_DISABLE immediately active
  • From: Mike Rapoprt <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mm: make PR_SET_THP_DISABLE immediately active
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] mm: make PR_SET_THP_DISABLE immediately active
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mm: make PR_SET_THP_DISABLE immediately active
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH] mm: make PR_SET_THP_DISABLE immediately active
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mm: make PR_SET_THP_DISABLE immediately active
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH] mm: make PR_SET_THP_DISABLE immediately active
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v7 2/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN
  • From: Matt Brown <matt@xxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v7 2/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v7 2/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN
  • From: Matt Brown <matt@xxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v7 2/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v7 2/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN
  • From: Matt Brown <matt@xxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v7 2/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• [PATCH] mm: make PR_SET_THP_DISABLE immediately active
  • From: "Mike Rapoport" <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [musl] Re: [PATCH resent] uapi libc compat: allow non-glibc to opt out of uapi definitions
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v4 next 1/3] modules:capabilities: allow __request_module() to take a capability argument
  • From: Kees Cook <keescook@xxxxxxxxxx>
• Re: [PATCH v4 next 1/3] modules:capabilities: allow __request_module() to take a capability argument
  • From: Djalal Harouni <tixxdz@xxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Andrea Arcangeli <aarcange@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] KEYS: make keyctl_invalidate() also require Setattr permission
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Andrea Arcangeli <aarcange@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Andrea Arcangeli <aarcange@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Mike Rapoprt <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Mike Rapoprt <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 09/10] xfs: nowait aio support
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v4 next 1/3] modules:capabilities: allow __request_module() to take a capability argument
  • From: Kees Cook <keescook@xxxxxxxxxx>
• Re: [PATCH 09/10] xfs: nowait aio support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Andrea Arcangeli <aarcange@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Andrea Arcangeli <aarcange@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Andrea Arcangeli <aarcange@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] ALSA: Adjust structure(snd_timer_tread) members to avoid 8 padding bytes
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [PATCH] ALSA: Adjust structure(snd_timer_tread) members to avoid 8 padding bytes
  • From: Manjeet Pawar <manjeet.p@xxxxxxxxxxx>
• Re: [PATCH v2] mm: introduce MADV_RESET_HUGEPAGE
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• Re: [PATCH 09/10] xfs: nowait aio support
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 0/10 v9] No wait AIO
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 09/10] xfs: nowait aio support
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH v2] mm: introduce MADV_RESET_HUGEPAGE
  • From: "Mike Rapoport" <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/10 v9] No wait AIO
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 09/10] xfs: nowait aio support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH v2] ioctl_getfsmap.2: document the GETFSMAP ioctl
  • From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
• Re: [PATCH 09/10] xfs: nowait aio support
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 0/10 v9] No wait AIO
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Fuzzey, Martin" <mfuzzey@xxxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH 06/10] fs: Introduce IOMAP_NOWAIT
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 05/10] fs: return if direct write will trigger writeback
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 04/10] fs: Introduce RWF_NOWAIT
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Fuzzey, Martin" <mfuzzey@xxxxxxxxxxx>
• Re: [PATCH 03/10] fs: Use RWF_* flags for AIO operations
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 02/10] fs: Introduce filemap_range_has_page()
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 01/10] fs: Separate out kiocb flags setup based on RWF_* flags
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions
  • From: Djalal Harouni <tixxdz@xxxxxxxxx>
• Re: [PATCH 09/10] xfs: nowait aio support
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH 01/10] fs: Separate out kiocb flags setup based on RWF_* flags
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 03/10] fs: Use RWF_* flags for AIO operations
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 02/10] fs: Introduce filemap_range_has_page()
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 05/10] fs: return if direct write will trigger writeback
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 07/10] fs: return on congested block device
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 09/10] xfs: nowait aio support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 10/10] btrfs: nowait aio support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 06/10] fs: Introduce IOMAP_NOWAIT
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 04/10] fs: Introduce RWF_NOWAIT
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 08/10] ext4: nowait aio support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 0/10 v9] No wait AIO
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Andrea Arcangeli <aarcange@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Pavel Emelyanov <xemul@xxxxxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Pavel Emelyanov <xemul@xxxxxxxxxxxxx>
• Re: [PATCH v4 next 1/3] modules:capabilities: allow __request_module() to take a capability argument
  • From: Djalal Harouni <tixxdz@xxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] fault-inject: support systematic fault injection
  • From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
• [PATCHv6 10/10] x86/mm: Allow to have userspace mappings above 47-bits
  • From: "Kirill A. Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
• Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• [PATCH 4.9 010/164] fanotify: dont expose EOPENSTALE to userspace
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• [RFC PATCH v2] fs: block dev aio request priority support
  • From: <adam.manzanares@xxxxxxx>
• [PATCH 4.11 009/197] fanotify: dont expose EOPENSTALE to userspace
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH] [PATCH] namespaces.7: Document the /proc/[pid]/ns/pid_for_children file
  • From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
• Re: [PATCH v4 next 1/3] modules:capabilities: allow __request_module() to take a capability argument
  • From: Kees Cook <keescook@xxxxxxxxxx>
• Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions
  • From: Kees Cook <keescook@xxxxxxxxxx>
• Re: [RFC PATCH] fs: block dev aio request priority support
  • From: Adam Manzanares <adam.manzanares@xxxxxxx>
• Re: [PATCH v4 next 3/3] modules:capabilities: add a per-task modules auto-load mode
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions
  • From: Djalal Harouni <tixxdz@xxxxxxxxx>
• Re: [PATCH v2 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v4 next 1/3] modules:capabilities: allow __request_module() to take a capability argument
  • From: Djalal Harouni <tixxdz@xxxxxxxxx>
• Re: [RFC PATCH] fs: block dev aio request priority support
  • From: Jan Kara <jack@xxxxxxx>
• Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions
  • From: Solar Designer <solar@xxxxxxxxxxxx>
• Re: [PATCH v2 6/6] mm, mempolicy: don't check cpuset seqlock where it doesn't matter
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH v2 5/6] mm, cpuset: always use seqlock when changing task's nodemask
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH v2 4/6] mm, mempolicy: simplify rebinding mempolicies when updating cpusets
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 next 2/3] modules:capabilities: automatic module loading restriction
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 next 1/3] modules:capabilities: allow __request_module() to take a capability argument
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions
  • From: Djalal Harouni <tixxdz@xxxxxxxxx>
• [RFC PATCH] fs: block dev aio request priority support
  • From: <adam.manzanares@xxxxxxx>
• Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions
  • From: Solar Designer <solar@xxxxxxxxxxxx>
• Patch "fanotify: don't expose EOPENSTALE to userspace" has been added to the 4.9-stable tree
  • From: <gregkh@xxxxxxxxxxxxxxxxxxx>
• Patch "fanotify: don't expose EOPENSTALE to userspace" has been added to the 4.11-stable tree
  • From: <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions
  • From: Djalal Harouni <tixxdz@xxxxxxxxx>
• Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions
  • From: Solar Designer <solar@xxxxxxxxxxxx>
• [PATCH v4 next 2/3] modules:capabilities: automatic module loading restriction
  • From: Djalal Harouni <tixxdz@xxxxxxxxx>
• [PATCH v4 next 1/3] modules:capabilities: allow __request_module() to take a capability argument
  • From: Djalal Harouni <tixxdz@xxxxxxxxx>
• [PATCH v4 next 3/3] modules:capabilities: add a per-task modules auto-load mode
  • From: Djalal Harouni <tixxdz@xxxxxxxxx>
• [PATCH v4 next 0/3] modules: automatic module loading restrictions
  • From: Djalal Harouni <tixxdz@xxxxxxxxx>
• Re: [PATCH 03/23] uuid: remove uuid_be defintions from the uapi header
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v2 3/6] mm, page_alloc: pass preferred nid instead of zonelist to allocator
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH v2 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [RFC 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH 03/23] uuid: remove uuid_be defintions from the uapi header
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [RFC 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [RFC 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: [PATCHv5, REBASED 9/9] x86/mm: Allow to have userspace mappings above 47-bits
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [RFC 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCHv5, REBASED 9/9] x86/mm: Allow to have userspace mappings above 47-bits
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [RFC 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: [RFC 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: [PATCHv5, REBASED 9/9] x86/mm: Allow to have userspace mappings above 47-bits
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: [PATCHv5, REBASED 9/9] x86/mm: Allow to have userspace mappings above 47-bits
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCHv5, REBASED 9/9] x86/mm: Allow to have userspace mappings above 47-bits
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCHv5, REBASED 9/9] x86/mm: Allow to have userspace mappings above 47-bits
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: [PATCHv5, REBASED 9/9] x86/mm: Allow to have userspace mappings above 47-bits
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCHv5, REBASED 9/9] x86/mm: Allow to have userspace mappings above 47-bits
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• [PATCH] [PATCH] namespaces.7: Document the /proc/[pid]/ns/pid_for_children file
  • From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
• Re: [PATCHv5, REBASED 9/9] x86/mm: Allow to have userspace mappings above 47-bits
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH v2 3/6] mm, page_alloc: pass preferred nid instead of zonelist to allocator
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [RFC 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [RFC 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: new ...at() flag: AT_NO_JUMPS
  • From: David Drysdale <drysdale@xxxxxxxxxx>
• [PATCH v2] ioctl_getfsmap.2: document the GETFSMAP ioctl
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH] ioctl_getfsmap.2: document the GETFSMAP ioctl
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH v2 0/6] cpuset/mempolicies related fixes and cleanups
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [RFC 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: [RFC 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: [PATCH v2 3/6] mm, page_alloc: pass preferred nid instead of zonelist to allocator
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: [PATCH v2 2/6] mm, mempolicy: stop adjusting current->il_next in mpol_rebind_nodemask()
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: [RFC 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [RFC 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: [RFC 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [RFC 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: [RFC 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• [PATCH v2 4/6] mm, mempolicy: simplify rebinding mempolicies when updating cpusets
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• [PATCH v2 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• [PATCH v2 2/6] mm, mempolicy: stop adjusting current->il_next in mpol_rebind_nodemask()
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• [PATCH v2 3/6] mm, page_alloc: pass preferred nid instead of zonelist to allocator
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• [PATCH v2 6/6] mm, mempolicy: don't check cpuset seqlock where it doesn't matter
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• [PATCH v2 5/6] mm, cpuset: always use seqlock when changing task's nodemask
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• [PATCH v2 0/6] cpuset/mempolicies related fixes and cleanups
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH] KEYS: make keyctl_invalidate() also require Setattr permission
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: [PATCHv5, REBASED 9/9] x86/mm: Allow to have userspace mappings above 47-bits
  • From: "Kirill A. Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
• Re: [PATCHv5, REBASED 9/9] x86/mm: Allow to have userspace mappings above 47-bits
  • From: kbuild test robot <lkp@xxxxxxxxx>
• [PATCHv5, REBASED 9/9] x86/mm: Allow to have userspace mappings above 47-bits
  • From: "Kirill A. Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
• Re: [PATCH 04/10] fs: Introduce RWF_NOWAIT
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] selftests/vm: Fix test for virtual address range mapping for arm64
  • From: Michal Suchánek <msuchanek@xxxxxxx>
• Re: [PATCH] selftests/vm: Fix test for virtual address range mapping for arm64
  • From: Anshuman Khandual <khandual@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] ioctl_getfsmap.2: document the GETFSMAP ioctl
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH] ioctl_getfsmap.2: document the GETFSMAP ioctl
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH] ioctl_getfsmap.2: document the GETFSMAP ioctl
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [PATCH linux-next] kcmp: fs/epoll -- Wrap kcmp code with CONFIG_CHECKPOINT_RESTORE
  • From: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [patch v4 resend 2/2] kcmp: Add KCMP_EPOLL_TFD mode to compare epoll target files
  • From: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
• Re: [patch v4 resend 2/2] kcmp: Add KCMP_EPOLL_TFD mode to compare epoll target files
  • From: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
• Re: [patch v4 resend 2/2] kcmp: Add KCMP_EPOLL_TFD mode to compare epoll target files
  • From: Andrei Vagin <avagin@xxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [patch v4 resend 2/2] kcmp: Add KCMP_EPOLL_TFD mode to compare epoll target files
  • From: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
• Re: [patch v4 resend 2/2] kcmp: Add KCMP_EPOLL_TFD mode to compare epoll target files
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [patch v4 resend 2/2] kcmp: Add KCMP_EPOLL_TFD mode to compare epoll target files
  • From: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
• Re: [patch v4 resend 2/2] kcmp: Add KCMP_EPOLL_TFD mode to compare epoll target files
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Rik van Riel <riel@xxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Daniel Micay <danielmicay@xxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Daniel Micay <danielmicay@xxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• [PATCH v2 RFC] mnt: umount mounts one by one in umount_tree()
  • From: Andrei Vagin <avagin@xxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Thomas Garnier <thgarnie@xxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Martin Schwidefsky <schwidefsky@xxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Martin Schwidefsky <schwidefsky@xxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Thomas Garnier <thgarnie@xxxxxxxxxx>
• [PATCH 02/10] fs: Introduce filemap_range_has_page()
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 05/10] fs: return if direct write will trigger writeback
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 04/10] fs: Introduce RWF_NOWAIT
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 07/10] fs: return on congested block device
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 06/10] fs: Introduce IOMAP_NOWAIT
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 10/10] btrfs: nowait aio support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 08/10] ext4: nowait aio support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 09/10] xfs: nowait aio support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 03/10] fs: Use RWF_* flags for AIO operations
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 01/10] fs: Separate out kiocb flags setup based on RWF_* flags
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 0/10 v8] No wait AIO
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 5/8] nowait aio: return on congested block device
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH 7/8] nowait aio: xfs
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 5/8] nowait aio: return on congested block device
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 3/8] nowait aio: return if direct write will trigger writeback
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 2/8] nowait aio: Introduce RWF_NOWAIT
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 1/8] Use RWF_* flags for AIO operations
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH] ioctl_getfsmap.2: document the GETFSMAP ioctl
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: [PATCH] fs: add an ioctl to get an owning userns for a superblock
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH] fs: add an ioctl to get an owning userns for a superblock
  • From: Andrei Vagin <avagin@xxxxxxxxxxxxx>
• Re: [PATCH] mnt: allow to add a mount into an existing group
  • From: Andrei Vagin <avagin@xxxxxxxxxxxxx>
• Re: [PATCH] ioctl_getfsmap.2: document the GETFSMAP ioctl
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH] ioctl_getfsmap.2: document the GETFSMAP ioctl
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH] ioctl_getfsmap.2: document the GETFSMAP ioctl
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH] mnt: allow to add a mount into an existing group
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH] fs: add an ioctl to get an owning userns for a superblock
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• [PATCH] fs: add an ioctl to get an owning userns for a superblock
  • From: Andrei Vagin <avagin@xxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH] ioctl_getfsmap.2: document the GETFSMAP ioctl
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: [PATCH] selftests/vm: Fix test for virtual address range mapping for arm64
  • From: Shuah Khan <shuahkh@xxxxxxxxxxxxxxx>
• [PATCH] selftests/vm: Fix test for virtual address range mapping for arm64
  • From: Michal Suchanek <msuchanek@xxxxxxx>
• Re: [patch v4 resend 1/2] procfs: fdinfo -- Extend information about epoll target files
  • From: Andrei Vagin <avagin@xxxxxxxxxxxxx>
• Re: [PATCH] mnt: allow to add a mount into an existing group
  • From: Andrey Vagin <avagin@xxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Brian Gerst <brgerst@xxxxxxxxx>
• Re: [PATCH 6/8] nowait aio: ext4
  • From: Jan Kara <jack@xxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Thomas Garnier <thgarnie@xxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• [PATCH 0/8 v7] No wait AIO
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 2/8] nowait aio: Introduce RWF_NOWAIT
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 7/8] nowait aio: xfs
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 5/8] nowait aio: return on congested block device
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 4/8] nowait-aio: Introduce IOMAP_NOWAIT
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 3/8] nowait aio: return if direct write will trigger writeback
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 6/8] nowait aio: ext4
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 8/8] nowait aio: btrfs
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 1/8] Use RWF_* flags for AIO operations
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [PATCH] ioctl_getfsmap.2: document the GETFSMAP ioctl
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH] ioctl_getfsmap.2: document the GETFSMAP ioctl
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] ioctl_getfsmap.2: document the GETFSMAP ioctl
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Thomas Garnier <thgarnie@xxxxxxxxxx>
• Re: new ...at() flag: AT_NO_JUMPS
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH] ioctl_getfsmap.2: document the GETFSMAP ioctl
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH] ioctl_getfsmap.2: document the GETFSMAP ioctl
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
  • From: Kees Cook <keescook@xxxxxxxxxxxx>