Linux API

• Date Index

• Re: Can we drop upstream Linux x32 support?, (continued)
  • Re: Can we drop upstream Linux x32 support?, Thorsten Glaser
    • Re: Can we drop upstream Linux x32 support?, Arnd Bergmann
      • Re: Can we drop upstream Linux x32 support?, Joseph Myers
        • Re: Can we drop upstream Linux x32 support?, Ivan Ivanov
          • Re: Can we drop upstream Linux x32 support?, Andy Lutomirski
            • Re: Can we drop upstream Linux x32 support?, Ivan Ivanov
    • Re: Can we drop upstream Linux x32 support?, Andy Lutomirski
      • Re: Can we drop upstream Linux x32 support?, Rich Felker
        • Re: Can we drop upstream Linux x32 support?, Andy Lutomirski
          • Re: Can we drop upstream Linux x32 support?, Catalin Marinas
            • Re: Can we drop upstream Linux x32 support?, Rich Felker
              • Re: Can we drop upstream Linux x32 support?, Florian Weimer
                • Re: Can we drop upstream Linux x32 support?, Rich Felker
                  • Re: Can we drop upstream Linux x32 support?, Florian Weimer
                    • Re: Can we drop upstream Linux x32 support?, Rich Felker
                • Re: Can we drop upstream Linux x32 support?, Joseph Myers
      • Re: Can we drop upstream Linux x32 support?, Thorsten Glaser
  • Re: Can we drop upstream Linux x32 support?, Maciej W. Rozycki
  • Re: Can we drop upstream Linux x32 support?, Olof Johansson
    • Re: Can we drop upstream Linux x32 support?, Lance Richardson
  • Re: Can we drop upstream Linux x32 support?, Richard Purdie
  • Re: Can we drop upstream Linux x32 support?, H.J. Lu
    • Re: Can we drop upstream Linux x32 support?, Andy Lutomirski
      • Re: Can we drop upstream Linux x32 support?, Arnd Bergmann
        • Re: Can we drop upstream Linux x32 support?, Catalin Marinas
          • Re: Can we drop upstream Linux x32 support?, Florian Weimer
            • Re: Can we drop upstream Linux x32 support?, Catalin Marinas
  • Re: Can we drop upstream Linux x32 support?, Christian Brauner
  • Re: Can we drop upstream Linux x32 support?, John Paul Adrian Glaubitz
    • Re: Can we drop upstream Linux x32 support?, Florian Weimer
      • Re: Can we drop upstream Linux x32 support?, John Paul Adrian Glaubitz
    • Re: Can we drop upstream Linux x32 support?, Thorsten Glaser
      • Re: Can we drop upstream Linux x32 support?, Rich Felker
    • Re: Can we drop upstream Linux x32 support?, Kevin Easton
      • Re: Can we drop upstream Linux x32 support?, Richard Weinberger
        • Re: Can we drop upstream Linux x32 support?, Kevin Easton
        • RE: Can we drop upstream Linux x32 support?, David Laight
          • Re: Can we drop upstream Linux x32 support?, Richard Weinberger
    • Re: Can we drop upstream Linux x32 support?, Rich Felker
      • Re: Can we drop upstream Linux x32 support?, Bernd Petrovitsch
        • Re: Can we drop upstream Linux x32 support?, Rich Felker
          • Re: Can we drop upstream Linux x32 support?, Bernd Petrovitsch
          • Re: Can we drop upstream Linux x32 support?, Florian Weimer
            • Re: Can we drop upstream Linux x32 support?, Rich Felker
              • Re: Can we drop upstream Linux x32 support?, Andy Lutomirski
                • Re: Can we drop upstream Linux x32 support?, Lance Richardson
                • Re: Can we drop upstream Linux x32 support?, Linus Torvalds
                  • Re: Can we drop upstream Linux x32 support?, Andy Lutomirski
  • Re: Can we drop upstream Linux x32 support?, Thomas Schöbel-Theuer
    • Re: Can we drop upstream Linux x32 support?, Andy Lutomirski
      • Re: Can we drop upstream Linux x32 support?, Thomas Schöbel-Theuer
        • Re: Can we drop upstream Linux x32 support?, Thomas Schoebel-Theuer
          • Re: Can we drop upstream Linux x32 support?, Andy Lutomirski
    • Re: Can we drop upstream Linux x32 support?, Florian Weimer
      • Re: Can we drop upstream Linux x32 support?, Rich Felker
    • Re: Can we drop upstream Linux x32 support?, Enrico Weigelt, metux IT consult
• [PATCH v5 0/5] cgroup: Introducing bypass mode, Waiman Long
  • [PATCH v5 3/5] cgroup: Make debug controller report new controller masks, Waiman Long
  • [PATCH v5 4/5] sched/core: Make cpu cgroup controller bypassable, Waiman Long
  • [PATCH v5 5/5] cgroup: Document bypass mode, Waiman Long
  • [PATCH v5 1/5] cgroup: subtree_control bypass mode for bypassable controllers, Waiman Long
  • [PATCH v5 2/5] cgroup: Allow reenabling of controller in bypass mode, Waiman Long
• [PATCH v5 24/25] ptrace: add PTRACE_GET_SYSCALL_INFO request, Dmitry V. Levin
  • Re: [PATCH v5 24/25] ptrace: add PTRACE_GET_SYSCALL_INFO request, Oleg Nesterov
    • Re: [PATCH v5 24/25] ptrace: add PTRACE_GET_SYSCALL_INFO request, Dmitry V. Levin
      • Re: [PATCH v5 24/25] ptrace: add PTRACE_GET_SYSCALL_INFO request, Oleg Nesterov
        • Re: [PATCH v5 24/25] ptrace: add PTRACE_GET_SYSCALL_INFO request, Dmitry V. Levin
          • Re: [PATCH v5 24/25] ptrace: add PTRACE_GET_SYSCALL_INFO request, Dmitry V. Levin
            • Re: [PATCH v5 24/25] ptrace: add PTRACE_GET_SYSCALL_INFO request, Oleg Nesterov
  • Re: [PATCH v5 24/25] ptrace: add PTRACE_GET_SYSCALL_INFO request, kbuild test robot
    • Re: [PATCH v5 24/25] ptrace: add PTRACE_GET_SYSCALL_INFO request, Dmitry V. Levin
      • Re: [PATCH v5 24/25] ptrace: add PTRACE_GET_SYSCALL_INFO request, Paul Burton
        • Re: [PATCH v5 24/25] ptrace: add PTRACE_GET_SYSCALL_INFO request, Palmer Dabbelt
      • Re: [PATCH v5 24/25] ptrace: add PTRACE_GET_SYSCALL_INFO request, Andy Lutomirski
  • Re: [PATCH v5 24/25] ptrace: add PTRACE_GET_SYSCALL_INFO request, Kees Cook
  • Re: [PATCH v5 24/25] ptrace: add PTRACE_GET_SYSCALL_INFO request, kbuild test robot
• [PATCH v10 0/4] seccomp trap to userspace, Tycho Andersen
  • [PATCH v10 2/4] seccomp: switch system call argument type to void *, Tycho Andersen
    • Re: [PATCH v10 2/4] seccomp: switch system call argument type to void *, Kees Cook
  • [PATCH v10 4/4] samples: add an example of seccomp user trap, Tycho Andersen
    • Re: [PATCH v10 4/4] samples: add an example of seccomp user trap, Serge E. Hallyn
      • Re: [PATCH v10 4/4] samples: add an example of seccomp user trap, Kees Cook
  • [PATCH v10 3/4] seccomp: add a return code to trap to userspace, Tycho Andersen
    • Re: [PATCH v10 3/4] seccomp: add a return code to trap to userspace, Kees Cook
  • [PATCH v10 1/4] seccomp: hoist struct seccomp_data recalculation higher, Tycho Andersen
    • Re: [PATCH v10 1/4] seccomp: hoist struct seccomp_data recalculation higher, Kees Cook
• [GIT PULL] asm-generic: bugfix for asm/unistd.h, Arnd Bergmann
  • Re: [GIT PULL] asm-generic: bugfix for asm/unistd.h, pr-tracker-bot
• [PATCH v5 0/1] signaling processes through pidfds, Christian Brauner
  • [PATCH v5 1/1] signal: add pidfd_send_signal() syscall, Christian Brauner
    • Re: [PATCH v5 1/1] signal: add pidfd_send_signal() syscall, kbuild test robot
    • Re: [PATCH v5 1/1] signal: add pidfd_send_signal() syscall, Serge E. Hallyn
      • Re: [PATCH v5 1/1] signal: add pidfd_send_signal() syscall, Christian Brauner
• [PATCH 0/5] y2038: further system call conversion, Arnd Bergmann
  • [PATCH 5/5] y2038: signal: Add compat_sys_rt_sigtimedwait_time64, Arnd Bergmann
  • [PATCH 3/5] y2038: socket: Add compat_sys_recvmmsg_time64, Arnd Bergmann
  • [PATCH 1/5] y2038: futex: Move compat implementation into futex.c, Arnd Bergmann
  • [PATCH 2/5] y2038: futex: Add support for __kernel_timespec, Arnd Bergmann
  • [PATCH 4/5] y2038: signal: Add sys_rt_sigtimedwait_time32, Arnd Bergmann
• [PATCH v4] signal: add taskfd_send_signal() syscall, Christian Brauner
  • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Florian Weimer
    • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Jürg Billeter
      • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Florian Weimer
        • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Jürg Billeter
          • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Florian Weimer
        • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Eric W. Biederman
          • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Florian Weimer
            • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Aleksa Sarai
            • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Eric W. Biederman
    • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Christian Brauner
      • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Florian Weimer
  • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Eric W. Biederman
    • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Daniel Colascione
      • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Eric W. Biederman
        • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Christian Brauner
          • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Kees Cook
            • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Serge E. Hallyn
    • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Christian Brauner
      • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Eric W. Biederman
        • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Christian Brauner
          • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Eric W. Biederman
            • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Daniel Colascione
              • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Eric W. Biederman
                • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Daniel Colascione
            • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Christian Brauner
              • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Eric W. Biederman
                • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Daniel Colascione
                • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Christian Brauner
                  • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Christian Brauner
                    • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Serge E. Hallyn
                      • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Daniel Colascione
                        • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Serge E. Hallyn
                          • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Daniel Colascione
                            • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Christian Brauner
                              • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Serge E. Hallyn
  • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, Serge E. Hallyn
  • Re: [PATCH v4] signal: add taskfd_send_signal() syscall, kbuild test robot
• Re: [PATCH] Y2038: provide kernel support indication, Arnd Bergmann
  • Re: [PATCH] Y2038: provide kernel support indication, Joseph Myers
    • Re: [PATCH] Y2038: provide kernel support indication, Arnd Bergmann
      • Re: [PATCH] Y2038: provide kernel support indication, Joseph Myers
• [PATCH v3] signal: add procfd_send_signal() syscall, Christian Brauner
  • Re: [PATCH v3] signal: add procfd_send_signal() syscall, kbuild test robot
  • Re: [PATCH v3] signal: add procfd_send_signal() syscall, Eric W. Biederman
  • Re: [PATCH v3] signal: add procfd_send_signal() syscall, Eric W. Biederman
    • Re: [PATCH v3] signal: add procfd_send_signal() syscall, Christian Brauner
      • Re: [PATCH v3] signal: add procfd_send_signal() syscall, Kees Cook
        • Re: [PATCH v3] signal: add procfd_send_signal() syscall, Christian Brauner
          • Re: [PATCH v3] signal: add procfd_send_signal() syscall, Kees Cook
• [RFC PATCH glibc 1/4] glibc: Perform rseq(2) registration at nptl init and thread creation (v4), Mathieu Desnoyers
  • [RFC PATCH glibc 2/4] glibc: sched_getcpu(): use rseq cpu_id TLS on Linux, Mathieu Desnoyers
  • Re: [RFC PATCH glibc 1/4] glibc: Perform rseq(2) registration at nptl init and thread creation (v4), Florian Weimer
    • Re: [RFC PATCH glibc 1/4] glibc: Perform rseq(2) registration at nptl init and thread creation (v4), Mathieu Desnoyers
  • Re: [RFC PATCH glibc 1/4] glibc: Perform rseq(2) registration at nptl init and thread creation (v4), Florian Weimer
    • Re: [RFC PATCH glibc 1/4] glibc: Perform rseq(2) registration at nptl init and thread creation (v4), Mathieu Desnoyers
      • Re: [RFC PATCH glibc 1/4] glibc: Perform rseq(2) registration at nptl init and thread creation (v4), Mathieu Desnoyers
        • Re: [RFC PATCH glibc 1/4] glibc: Perform rseq(2) registration at nptl init and thread creation (v4), Florian Weimer
      • Re: [RFC PATCH glibc 1/4] glibc: Perform rseq(2) registration at nptl init and thread creation (v4), Florian Weimer
        • Re: [RFC PATCH glibc 1/4] glibc: Perform rseq(2) registration at nptl init and thread creation (v4), Mathieu Desnoyers
          • Re: [RFC PATCH glibc 1/4] glibc: Perform rseq(2) registration at nptl init and thread creation (v4), Florian Weimer
            • Re: [RFC PATCH glibc 1/4] glibc: Perform rseq(2) registration at nptl init and thread creation (v4), Mathieu Desnoyers
• [PATCH 12/11] man-pages: copy_file_range updates, Dave Chinner
  • Re: [PATCH 12/11] man-pages: copy_file_range updates, Amir Goldstein
  • Re: [PATCH 12/11] man-pages: copy_file_range updates, Amir Goldstein
• Re: [PATCH 2/3] generic/43[014]: copy_range beyond source EOF should fail, Amir Goldstein
  • Re: [PATCH 2/3] generic/43[014]: copy_range beyond source EOF should fail, Dave Chinner
• [PATCH v9 0/4] seccomp trap to userspace, Tycho Andersen
  • [PATCH v9 3/4] seccomp: add a return code to trap to userspace, Tycho Andersen
    • Re: [PATCH v9 3/4] seccomp: add a return code to trap to userspace, Serge E. Hallyn
      • Re: [PATCH v9 3/4] seccomp: add a return code to trap to userspace, Tycho Andersen
        • Re: [PATCH v9 3/4] seccomp: add a return code to trap to userspace, Serge E. Hallyn
  • [PATCH v9 4/4] samples: add an example of seccomp user trap, Tycho Andersen
  • [PATCH v9 2/4] seccomp: switch system call argument type to void *, Tycho Andersen
    • Re: [PATCH v9 2/4] seccomp: switch system call argument type to void *, Serge E. Hallyn
      • Re: [PATCH v9 2/4] seccomp: switch system call argument type to void *, Paul Moore
    • Re: [PATCH v9 2/4] seccomp: switch system call argument type to void *, kbuild test robot
      • Re: [PATCH v9 2/4] seccomp: switch system call argument type to void *, Tycho Andersen
        • Re: [PATCH v9 2/4] seccomp: switch system call argument type to void *, Tycho Andersen
  • [PATCH v9 1/4] seccomp: hoist struct seccomp_data recalculation higher, Tycho Andersen
    • Re: [PATCH v9 1/4] seccomp: hoist struct seccomp_data recalculation higher, Serge E. Hallyn
• [PATCH v4 00/15] fanotify: add support for more event types, Amir Goldstein
  • [PATCH v4 07/15] fanotify: copy event fid info to user, Amir Goldstein
    • Re: [PATCH v4 07/15] fanotify: copy event fid info to user, Jan Kara
      • Re: [PATCH v4 07/15] fanotify: copy event fid info to user, Amir Goldstein
  • [PATCH v4 08/15] fanotify: enable FAN_REPORT_FID init flag, Amir Goldstein
    • Re: [PATCH v4 08/15] fanotify: enable FAN_REPORT_FID init flag, Amir Goldstein
      • Re: [PATCH v4 08/15] fanotify: enable FAN_REPORT_FID init flag, Jan Kara
        • Re: [PATCH v4 08/15] fanotify: enable FAN_REPORT_FID init flag, Matthew Bobrowski
          • Re: [PATCH v4 08/15] fanotify: enable FAN_REPORT_FID init flag, Amir Goldstein
  • [PATCH v4 14/15] fanotify: add support for create/attrib/move/delete events, Amir Goldstein
    • Re: [PATCH v4 14/15] fanotify: add support for create/attrib/move/delete events, Jan Kara
  • [PATCH v4 15/15] fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID, Amir Goldstein
    • Re: [PATCH v4 15/15] fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID, Jan Kara
      • Re: [PATCH v4 15/15] fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID, Amir Goldstein
        • Re: [PATCH v4 15/15] fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID, Jan Kara
          • Re: [PATCH v4 15/15] fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID, Amir Goldstein
            • Re: [PATCH v4 15/15] fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID, Matthew Bobrowski
              • Re: [PATCH v4 15/15] fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID, Amir Goldstein
          • Re: [PATCH v4 15/15] fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID, Amir Goldstein
        • Re: [PATCH v4 15/15] fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID, Jan Kara
        • Re: [PATCH v4 15/15] fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID, Matthew Bobrowski
          • Re: [PATCH v4 15/15] fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID, Amir Goldstein
            • Re: [PATCH v4 15/15] fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID, Matthew Bobrowski
              • Re: [PATCH v4 15/15] fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID, Amir Goldstein
  • Re: [PATCH v4 00/15] fanotify: add support for more event types, Jan Kara
    • Re: [PATCH v4 00/15] fanotify: add support for more event types, Amir Goldstein
      • Re: [PATCH v4 00/15] fanotify: add support for more event types, Jan Kara
        • Re: [PATCH v4 00/15] fanotify: add support for more event types, Amir Goldstein
          • Re: [PATCH v4 00/15] fanotify: add support for more event types, Amir Goldstein
            • Re: [PATCH v4 00/15] fanotify: add support for more event types, Jan Kara
              • Re: [PATCH v4 00/15] fanotify: add support for more event types, Amir Goldstein
                • Re: [PATCH v4 00/15] fanotify: add support for more event types, Jan Kara
                  • Re: [PATCH v4 00/15] fanotify: add support for more event types, Amir Goldstein
          • Re: [PATCH v4 00/15] fanotify: add support for more event types, Jan Kara
            • Re: [PATCH v4 00/15] fanotify: add support for more event types, Amir Goldstein
• Security modules and sending signals within the same process, Florian Weimer
  • Re: Security modules and sending signals within the same process, Stephen Smalley
    • Re: Security modules and sending signals within the same process, Florian Weimer
  • Re: Security modules and sending signals within the same process, Casey Schaufler
    • Re: Security modules and sending signals within the same process, Florian Weimer
    • Re: [apparmor] Security modules and sending signals within the same process, John Johansen
• [PATCH v4 0/2] ptrace: add PTRACE_GET_SYSCALL_INFO request, Dmitry V. Levin
  • [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message, Dmitry V. Levin
    • Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message, Oleg Nesterov
      • Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message, Dmitry V. Levin
        • Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message, Oleg Nesterov
          • Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message, Dmitry V. Levin
            • Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message, Dmitry V. Levin
              • Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message, Andy Lutomirski
                • Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message, Dmitry V. Levin
                • Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message, Oleg Nesterov
              • Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message, Oleg Nesterov
                • Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message, Dmitry V. Levin
                  • Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message, Oleg Nesterov
                    • Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message, Dmitry V. Levin
  • [PATCH v4 2/2] ptrace: add PTRACE_GET_SYSCALL_INFO request, Dmitry V. Levin
    • Re: [PATCH v4 2/2] ptrace: add PTRACE_GET_SYSCALL_INFO request, Oleg Nesterov
      • Re: [PATCH v4 2/2] ptrace: add PTRACE_GET_SYSCALL_INFO request, Oleg Nesterov
• [PATCH 0/1] Add prctl to kill descendants on exit, Jürg Billeter
  • [PATCH] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT, Jürg Billeter
    • Re: [PATCH] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT, Oleg Nesterov
      • Re: [PATCH] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT, Eric W. Biederman
        • Re: [PATCH] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT, Oleg Nesterov
          • Re: [PATCH] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT, Jürg Billeter
            • Re: [PATCH] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT, Oleg Nesterov
              • Re: [PATCH] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT, Kees Cook
    • [PATCH v2 0/1] Add prctl to kill descendants on exit, Jürg Billeter
      • [PATCH v2 1/1] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT, Jürg Billeter
        • Re: [PATCH v2 1/1] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT, Oleg Nesterov
        • Re: [PATCH v2 1/1] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT, Florian Weimer
          • Re: [PATCH v2 1/1] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT, Jürg Billeter
            • Re: [PATCH v2 1/1] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT, Florian Weimer
              • Re: [PATCH v2 1/1] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT, Jürg Billeter
      • Re: [PATCH v2 0/1] Add prctl to kill descendants on exit, Jürg Billeter
  • [RESEND PATCH v2 0/1] Add prctl to kill descendants on exit, Jürg Billeter
    • [RESEND PATCH v2 1/1] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT, Jürg Billeter
      • Re: [RESEND PATCH v2 1/1] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT, Andrew Morton
• [PATCH v3 00/13] fanotify: add support for more event types, Amir Goldstein
  • [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier, Amir Goldstein
    • Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier, Jan Kara
      • Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier, Amir Goldstein
        • Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier, Jan Kara
          • Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier, Amir Goldstein
            • Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier, Jan Kara
              • Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier, Amir Goldstein
                • Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier, Jan Kara
                  • Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier, Amir Goldstein
                  • Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier, Amir Goldstein
                    • Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier, Amir Goldstein
  • [PATCH v3 08/13] fanotify: enable FAN_REPORT_FID init flag, Amir Goldstein
    • Re: [PATCH v3 08/13] fanotify: enable FAN_REPORT_FID init flag, Jan Kara
      • Re: [PATCH v3 08/13] fanotify: enable FAN_REPORT_FID init flag, Amir Goldstein
        • Re: [PATCH v3 08/13] fanotify: enable FAN_REPORT_FID init flag, Jan Kara
      • Re: [PATCH v3 08/13] fanotify: enable FAN_REPORT_FID init flag, Jan Kara
  • [PATCH v3 12/13] fanotify: add support for create/attrib/move/delete events, Amir Goldstein
  • [PATCH v3 13/13] fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID, Amir Goldstein
• [PATCH RESEND v3 0/3] ptrace: add PTRACE_GET_SYSCALL_INFO request, Elvira Khabirova
  • [PATCH RESEND v3 1/3] ptrace: pass type of a syscall-stop in ptrace_message, Elvira Khabirova
    • Re: [PATCH RESEND v3 1/3] ptrace: pass type of a syscall-stop in ptrace_message, Joey Pabalinas
      • Re: [PATCH RESEND v3 1/3] ptrace: pass type of a syscall-stop in ptrace_message, Dmitry V. Levin
        • Re: Re: [PATCH RESEND v3 1/3] ptrace: pass type of a syscall-stop in ptrace_message, Joey Pabalinas
    • Re: [PATCH RESEND v3 1/3] ptrace: pass type of a syscall-stop in ptrace_message, Oleg Nesterov
      • Re: [PATCH RESEND v3 1/3] ptrace: pass type of a syscall-stop in ptrace_message, Elvira Khabirova
        • Re: [PATCH RESEND v3 1/3] ptrace: pass type of a syscall-stop in ptrace_message, Dmitry V. Levin
  • [PATCH RESEND v3 2/3] ptrace: add PTRACE_GET_SYSCALL_INFO request, Elvira Khabirova
  • [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO, Elvira Khabirova
    • Re: [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO, Oleg Nesterov
      • Re: [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO, Elvira Khabirova
        • Re: [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO, Dmitry V. Levin
        • Re: [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO, Oleg Nesterov
          • Re: [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO, Dmitry V. Levin
            • Re: [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO, Oleg Nesterov
              • Re: [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO, Dmitry V. Levin
                • Re: [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO, Oleg Nesterov
• Re: [RFC PATCH v2] ptrace: add PTRACE_GET_SYSCALL_INFO request, Andy Lutomirski
  • Re: [RFC PATCH v2] ptrace: add PTRACE_GET_SYSCALL_INFO request, Dmitry V. Levin
    • Re: [RFC PATCH v2] ptrace: add PTRACE_GET_SYSCALL_INFO request, Andy Lutomirski
      • Re: [RFC PATCH v2] ptrace: add PTRACE_GET_SYSCALL_INFO request, Dmitry V. Levin
        • Re: [RFC PATCH v2] ptrace: add PTRACE_GET_SYSCALL_INFO request, Andy Lutomirski
          • Re: [RFC PATCH v2] ptrace: add PTRACE_GET_SYSCALL_INFO request, Dmitry V. Levin
            • Re: [RFC PATCH v2] ptrace: add PTRACE_GET_SYSCALL_INFO request, Dmitry V. Levin
              • Re: [RFC PATCH v2] ptrace: add PTRACE_GET_SYSCALL_INFO request, Kees Cook
• [PATCH] Add /proc/pid_generation, Daniel Colascione
  • Re: [PATCH] Add /proc/pid_generation, Matthew Wilcox
    • Re: [PATCH] Add /proc/pid_generation, Daniel Colascione
      • Re: [PATCH] Add /proc/pid_generation, Matthew Wilcox
        • Re: [PATCH] Add /proc/pid_generation, Pavel Machek
  • [PATCH v2] Add /proc/pid_gen, Daniel Colascione
    • Re: [PATCH v2] Add /proc/pid_gen, Andrew Morton
      • Re: [PATCH v2] Add /proc/pid_gen, Daniel Colascione
        • Re: [PATCH v2] Add /proc/pid_gen, Jann Horn
          • Re: [PATCH v2] Add /proc/pid_gen, Daniel Colascione
        • Re: [PATCH v2] Add /proc/pid_gen, Andrew Morton
          • Re: [PATCH v2] Add /proc/pid_gen, Daniel Colascione
            • Re: [PATCH v2] Add /proc/pid_gen, Andy Lutomirski
              • Re: [PATCH v2] Add /proc/pid_gen, Daniel Colascione
              • Re: [PATCH v2] Add /proc/pid_gen, Cyrill Gorcunov
            • Re: [PATCH v2] Add /proc/pid_gen, Andrew Morton
              • Re: [PATCH v2] Add /proc/pid_gen, Daniel Colascione
                • Re: [PATCH v2] Add /proc/pid_gen, Daniel Colascione
                  • Re: [PATCH v2] Add /proc/pid_gen, Mathieu Desnoyers
                • Re: [PATCH v2] Add /proc/pid_gen, Andrew Morton
                  • Re: [PATCH v2] Add /proc/pid_gen, Daniel Colascione
                    • Re: [PATCH v2] Add /proc/pid_gen, Andrew Morton
                      • Re: [PATCH v2] Add /proc/pid_gen, Tim Murray
                        • Re: [PATCH v2] Add /proc/pid_gen, Daniel Colascione
  • Re: [PATCH] Add /proc/pid_generation, Kevin Easton
    • RE: [PATCH] Add /proc/pid_generation, David Laight
      • Re: [PATCH] Add /proc/pid_generation, Pavel Machek
• [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Mathieu Desnoyers
  • [RFC PATCH v4 2/5] glibc: sched_getcpu(): use rseq cpu_id TLS on Linux, Mathieu Desnoyers
  • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Rich Felker
    • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Mathieu Desnoyers
      • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Florian Weimer
        • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Rich Felker
          • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Florian Weimer
            • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Mathieu Desnoyers
              • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Rich Felker
              • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Szabolcs Nagy
                • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Mathieu Desnoyers
                  • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Rich Felker
                    • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Mathieu Desnoyers
      • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Rich Felker
        • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Mathieu Desnoyers
          • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Florian Weimer
            • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Mathieu Desnoyers
              • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Florian Weimer
                • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Rich Felker
                  • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Florian Weimer
                    • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Rich Felker
                      • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Mathieu Desnoyers
                        • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Rich Felker
                          • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Florian Weimer
                            • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Rich Felker
                              • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Florian Weimer
                          • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Mathieu Desnoyers
                            • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Rich Felker
                              • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Mathieu Desnoyers
                                • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Florian Weimer
                                • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Mathieu Desnoyers
                                • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Florian Weimer
                                • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Rich Felker
                                • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Mathieu Desnoyers
                                • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Mathieu Desnoyers
                                • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Mathieu Desnoyers
                                • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Rich Felker
                                • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Mathieu Desnoyers
                                • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Szabolcs Nagy
                • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Mathieu Desnoyers
                  • Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation, Florian Weimer
• Re: [PATCH v4 0/5] cgroup: Introducing bypass mode, Michael Kerrisk
• [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
  • [PATCH v2] procfd_signal.2: document procfd_signal syscall, Christian Brauner
  • Re: [PATCH v2] signal: add procfd_signal() syscall, Serge E. Hallyn
  • Re: [PATCH v2] signal: add procfd_signal() syscall, Aleksa Sarai
  • Re: [PATCH v2] signal: add procfd_signal() syscall, Arnd Bergmann
  • Re: [PATCH v2] signal: add procfd_signal() syscall, Florian Weimer
    • Re: [PATCH v2] signal: add procfd_signal() syscall, Andy Lutomirski
      • Re: [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
        • Re: [PATCH v2] signal: add procfd_signal() syscall, Andy Lutomirski
          • Re: [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
            • Re: [PATCH v2] signal: add procfd_signal() syscall, Andy Lutomirski
              • Re: [PATCH v2] signal: add procfd_signal() syscall, Arnd Bergmann
                • Re: [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
                  • Re: [PATCH v2] signal: add procfd_signal() syscall, Arnd Bergmann
                    • Re: [PATCH v2] signal: add procfd_signal() syscall, Aleksa Sarai
                    • Re: [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
                • Re: [PATCH v2] signal: add procfd_signal() syscall, Eric W. Biederman
                  • Re: [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
                    • Re: [PATCH v2] signal: add procfd_signal() syscall, Arnd Bergmann
                      • Re: [PATCH v2] signal: add procfd_signal() syscall, Andy Lutomirski
                        • Re: [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
                        • Re: [PATCH v2] signal: add procfd_signal() syscall, Arnd Bergmann
                          • Re: [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
                            • Re: [PATCH v2] signal: add procfd_signal() syscall, Daniel Colascione
                              • Re: [PATCH v2] signal: add procfd_signal() syscall, Arnd Bergmann
                                • Re: [PATCH v2] signal: add procfd_signal() syscall, Arnd Bergmann
                                • Re: [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
                                • Re: [PATCH v2] signal: add procfd_signal() syscall, Andy Lutomirski
                                • Re: [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
                          • Re: [PATCH v2] signal: add procfd_signal() syscall, Andy Lutomirski
                            • Re: [PATCH v2] signal: add procfd_signal() syscall, Arnd Bergmann
                              • Re: [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
                              • Re: [PATCH v2] signal: add procfd_signal() syscall, Arnd Bergmann
                        • Re: [PATCH v2] signal: add procfd_signal() syscall, Eric W. Biederman
                      • Re: [PATCH v2] signal: add procfd_signal() syscall, Eric W. Biederman
                        • Re: [PATCH v2] signal: add procfd_signal() syscall, Eric W. Biederman
                          • Re: [PATCH v2] signal: add procfd_signal() syscall, Andy Lutomirski
                            • Re: [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
                            • Re: [PATCH v2] signal: add procfd_signal() syscall, Eric W. Biederman
                              • Re: [PATCH v2] signal: add procfd_signal() syscall, Andy Lutomirski
                          • Re: [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
    • Re: [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
      • Re: [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
        • Re: [PATCH v2] signal: add procfd_signal() syscall, Florian Weimer
          • Re: [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
            • Re: [PATCH v2] signal: add procfd_signal() syscall, Aleksa Sarai
            • Re: [PATCH v2] signal: add procfd_signal() syscall, Florian Weimer
              • Re: [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
              • Re: [PATCH v2] signal: add procfd_signal() syscall, Andy Lutomirski
                • Re: [PATCH v2] signal: add procfd_signal() syscall, Florian Weimer
                  • Re: [PATCH v2] signal: add procfd_signal() syscall, Christian Brauner
                    • Re: [PATCH v2] signal: add procfd_signal() syscall, Lai Jiangshan
                      • Re: [PATCH v2] signal: add procfd_signal() syscall, Lai Jiangshan
                        • Re: [PATCH v2] signal: add procfd_signal() syscall, Aleksa Sarai
• [RFC PATCH 0/3] THP eligibility reporting via proc, Michal Hocko
  • [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc, Michal Hocko
    • Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc, Michal Hocko
    • Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc, Vlastimil Babka
    • Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc, William Kucharski
      • Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc, Michal Hocko
        • Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc, William Kucharski
          • Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc, Michal Hocko
          • Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc, Vlastimil Babka
            • Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc, William Kucharski
  • [RFC PATCH 2/3] mm, thp, proc: report THP eligibility for each vma, Michal Hocko
    • Re: [RFC PATCH 2/3] mm, thp, proc: report THP eligibility for each vma, Michal Hocko
    • Re: [RFC PATCH 2/3] mm, thp, proc: report THP eligibility for each vma, Vlastimil Babka
      • Re: [RFC PATCH 2/3] mm, thp, proc: report THP eligibility for each vma, Michal Hocko
        • Re: [RFC PATCH 2/3] mm, thp, proc: report THP eligibility for each vma, Vlastimil Babka
  • [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps, Michal Hocko
    • Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps, Jan Kara
      • Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps, Michal Hocko
      • Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps, David Rientjes
        • Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps, Michal Hocko
    • Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps, Dan Williams
      • Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps, Michal Hocko
        • Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps, Mike Rapoport
    • Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps, Mike Rapoport
      • Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps, Michal Hocko
    • Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps, Vlastimil Babka
  • Re: [RFC PATCH 0/3] THP eligibility reporting via proc, Michal Hocko
• [PATCH -manpage 1/2] fcntl.2: Update manpage with new memfd F_SEAL_FUTURE_WRITE seal, Joel Fernandes (Google)
  • [PATCH -manpage 2/2] memfd_create.2: Update manpage with new memfd F_SEAL_FUTURE_WRITE seal, Joel Fernandes (Google)
  • <Possible follow-ups>
  • [PATCH -manpage 1/2] fcntl.2: Update manpage with new memfd F_SEAL_FUTURE_WRITE seal, Joel Fernandes (Google)
    • [PATCH -manpage 2/2] memfd_create.2: Update manpage with new memfd F_SEAL_FUTURE_WRITE seal, Joel Fernandes (Google)
• [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust, Joel Fernandes (Google)
  • [PATCH -next 2/2] selftests/memfd: modify tests for F_SEAL_FUTURE_WRITE seal, Joel Fernandes (Google)
    • Re: [PATCH -next 2/2] selftests/memfd: modify tests for F_SEAL_FUTURE_WRITE seal, Joel Fernandes
  • Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust, Andy Lutomirski
    • Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust, Joel Fernandes
      • Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust, Stephen Rothwell
        • Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust, Andy Lutomirski
          • Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust, Joel Fernandes
            • Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust, Andy Lutomirski
              • Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust, Joel Fernandes
                • Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust, Andrew Morton
                  • Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust, Andy Lutomirski
                    • Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust, Joel Fernandes
                      • Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust, Andrew Morton
                        • Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust, Matthew Wilcox
                          • Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust, Joel Fernandes
• [RFC PATCH v6 00/11] Control-flow Enforcement: Branch Tracking, PTRACE, Yu-cheng Yu
  • [RFC PATCH v6 01/11] x86/cet/ibt: Add Kconfig option for user-mode Indirect Branch Tracking, Yu-cheng Yu
  • [RFC PATCH v6 02/11] x86/cet/ibt: User-mode indirect branch tracking support, Yu-cheng Yu
  • [RFC PATCH v6 03/11] x86/cet/ibt: Add IBT legacy code bitmap setup function, Yu-cheng Yu
  • [RFC PATCH v6 04/11] mm/mmap: Add IBT bitmap size to address space limit check, Yu-cheng Yu
  • [RFC PATCH v6 05/11] x86/cet/ibt: ELF header parsing for IBT, Yu-cheng Yu
  • [RFC PATCH v6 06/11] x86/cet/ibt: Add arch_prctl functions for IBT, Yu-cheng Yu
  • [RFC PATCH v6 07/11] x86/cet/ibt: Add ENDBR to op-code-map, Yu-cheng Yu
  • [RFC PATCH v6 08/11] x86: Insert endbr32/endbr64 to vDSO, Yu-cheng Yu
    • Re: [RFC PATCH v6 08/11] x86: Insert endbr32/endbr64 to vDSO, Andy Lutomirski
      • Re: [RFC PATCH v6 08/11] x86: Insert endbr32/endbr64 to vDSO, Yu-cheng Yu
  • [RFC PATCH v6 10/11] x86/vsyscall/64: Add ENDBR64 to vsyscall entry points, Yu-cheng Yu
    • Re: [RFC PATCH v6 10/11] x86/vsyscall/64: Add ENDBR64 to vsyscall entry points, Andy Lutomirski
  • [RFC PATCH v6 11/11] x86/cet: Add PTRACE interface for CET, Yu-cheng Yu
  • [RFC PATCH v6 09/11] x86/vsyscall/32: Add ENDBR32 to vsyscall entry point, Yu-cheng Yu
    • Re: [RFC PATCH v6 09/11] x86/vsyscall/32: Add ENDBR32 to vsyscall entry point, Andy Lutomirski
      • Re: [RFC PATCH v6 09/11] x86/vsyscall/32: Add ENDBR32 to vsyscall entry point, Yu-cheng Yu
• [RFC PATCH v6 00/26] Control-flow Enforcement: Shadow Stack, Yu-cheng Yu
  • [RFC PATCH v6 12/26] drm/i915/gvt: Update _PAGE_DIRTY to _PAGE_DIRTY_BITS, Yu-cheng Yu
  • [RFC PATCH v6 20/26] x86/cet/shstk: Introduce WRUSS instruction, Yu-cheng Yu
  • [RFC PATCH v6 19/26] x86/cet/shstk: User-mode shadow stack support, Yu-cheng Yu
  • [RFC PATCH v6 22/26] x86/cet/shstk: ELF header parsing of Shadow Stack, Yu-cheng Yu
    • Re: [RFC PATCH v6 22/26] x86/cet/shstk: ELF header parsing of Shadow Stack, Dave Martin
      • Re: [RFC PATCH v6 22/26] x86/cet/shstk: ELF header parsing of Shadow Stack, Yu-cheng Yu
        • Re: [RFC PATCH v6 22/26] x86/cet/shstk: ELF header parsing of Shadow Stack, Dave Martin
          • Re: [RFC PATCH v6 22/26] x86/cet/shstk: ELF header parsing of Shadow Stack, Dave Martin
          • Re: [RFC PATCH v6 22/26] x86/cet/shstk: ELF header parsing of Shadow Stack, Yu-cheng Yu
  • [RFC PATCH v6 24/26] mm/mmap: Add Shadow stack pages to memory accounting, Yu-cheng Yu
  • [RFC PATCH v6 25/26] x86/cet/shstk: Add arch_prctl functions for Shadow Stack, Yu-cheng Yu
  • [RFC PATCH v6 26/26] x86/cet/shstk: Add Shadow Stack instructions to opcode map, Yu-cheng Yu
  • [RFC PATCH v6 21/26] x86/cet/shstk: Signal handling for shadow stack, Yu-cheng Yu
  • [RFC PATCH v6 23/26] x86/cet/shstk: Handle thread shadow stack, Yu-cheng Yu
  • [RFC PATCH v6 17/26] mm: Update can_follow_write_pte/pmd for shadow stack, Yu-cheng Yu
  • [RFC PATCH v6 18/26] mm: Introduce do_mmap_locked(), Yu-cheng Yu
  • [RFC PATCH v6 15/26] mm: Handle shadow stack page fault, Yu-cheng Yu
  • [RFC PATCH v6 16/26] mm: Handle THP/HugeTLB shadow stack page fault, Yu-cheng Yu
  • [RFC PATCH v6 01/26] Documentation/x86: Add CET description, Yu-cheng Yu
    • Re: [RFC PATCH v6 01/26] Documentation/x86: Add CET description, Ingo Molnar
      • Re: [RFC PATCH v6 01/26] Documentation/x86: Add CET description, Yu-cheng Yu
        • Re: [RFC PATCH v6 01/26] Documentation/x86: Add CET description, Ingo Molnar
  • [RFC PATCH v6 02/26] x86/cpufeatures: Add CET CPU feature flags for Control-flow Enforcement Technology (CET), Yu-cheng Yu
  • [RFC PATCH v6 04/26] x86/fpu/xstate: Introduce XSAVES system states, Yu-cheng Yu
    • Re: [RFC PATCH v6 04/26] x86/fpu/xstate: Introduce XSAVES system states, Borislav Petkov
      • Re: [RFC PATCH v6 04/26] x86/fpu/xstate: Introduce XSAVES system states, Yu-cheng Yu
        • Re: [RFC PATCH v6 04/26] x86/fpu/xstate: Introduce XSAVES system states, Borislav Petkov
  • [RFC PATCH v6 06/26] x86/cet: Add control protection exception handler, Yu-cheng Yu
  • [RFC PATCH v6 05/26] x86/fpu/xstate: Add XSAVES system states for shadow stack, Yu-cheng Yu
  • [RFC PATCH v6 07/26] x86/cet/shstk: Add Kconfig option for user-mode shadow stack, Yu-cheng Yu
  • [RFC PATCH v6 09/26] mm/mmap: Prevent Shadow Stack VMA merges, Yu-cheng Yu
  • [RFC PATCH v6 11/26] x86/mm: Introduce _PAGE_DIRTY_SW, Yu-cheng Yu
  • [RFC PATCH v6 14/26] x86/mm: Shadow stack page fault error checking, Yu-cheng Yu
  • [RFC PATCH v6 13/26] x86/mm: Modify ptep_set_wrprotect and pmdp_set_wrprotect for _PAGE_DIRTY_SW, Yu-cheng Yu
  • [RFC PATCH v6 10/26] x86/mm: Change _PAGE_DIRTY to _PAGE_DIRTY_HW, Yu-cheng Yu
  • [RFC PATCH v6 08/26] mm: Introduce VM_SHSTK for shadow stack memory, Yu-cheng Yu
  • [RFC PATCH v6 03/26] x86/fpu/xstate: Change names to separate XSAVES system and user states, Yu-cheng Yu
  • Re: [RFC PATCH v6 00/26] Control-flow Enforcement: Shadow Stack, Andy Lutomirski
    • Re: [RFC PATCH v6 00/26] Control-flow Enforcement: Shadow Stack, Yu-cheng Yu
      • Re: [RFC PATCH v6 00/26] Control-flow Enforcement: Shadow Stack, Andy Lutomirski
• [PATCH v1 0/2] proc: allow signaling processes via file descriptors, Christian Brauner
  • [PATCH v1 1/2] proc: get process file descriptor from /proc/<pid>, Christian Brauner
    • Re: [PATCH v1 1/2] proc: get process file descriptor from /proc/<pid>, Andy Lutomirski
      • Re: [PATCH v1 1/2] proc: get process file descriptor from /proc/<pid>, Christian Brauner
  • [PATCH] procfd_signal.2: document procfd_signal syscall, Christian Brauner
    • Re: [PATCH] procfd_signal.2: document procfd_signal syscall, Michael Kerrisk (man-pages)
    • Re: [PATCH] procfd_signal.2: document procfd_signal syscall, Florian Weimer
      • Re: [PATCH] procfd_signal.2: document procfd_signal syscall, Christian Brauner
  • [PATCH v1 2/2] signal: add procfd_signal() syscall, Christian Brauner
    • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Andy Lutomirski
      • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Daniel Colascione
      • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Christian Brauner
    • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Daniel Colascione
      • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Christian Brauner
        • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Eric W. Biederman
          • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Christian Brauner
            • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Daniel Colascione
    • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Eugene Syromiatnikov
      • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Christian Brauner
    • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Eugene Syromiatnikov
    • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Aleksa Sarai
      • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Christian Brauner
        • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Christian Brauner
        • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Aleksa Sarai
          • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Christian Brauner
          • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Christian Brauner
            • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Aleksa Sarai
            • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Daniel Colascione
              • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Aleksa Sarai
              • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Christian Brauner
                • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Daniel Colascione
                  • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Eric W. Biederman
                    • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Christian Brauner
                      • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Serge E. Hallyn
          • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Aleksa Sarai
            • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Serge E. Hallyn
    • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Tycho Andersen
      • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Daniel Colascione
        • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Tycho Andersen
          • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Andy Lutomirski
            • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Christian Brauner
              • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Andy Lutomirski
            • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Daniel Colascione
      • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Serge E. Hallyn
    • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, kbuild test robot
      • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Christian Brauner
    • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, kbuild test robot
    • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Joey Pabalinas
      • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Christian Brauner
        • Re: [PATCH v1 2/2] signal: add procfd_signal() syscall, Joey Pabalinas
• [PATCH] proc: allow killing processes via file descriptors, Christian Brauner
  • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
    • Re: [PATCH] proc: allow killing processes via file descriptors, Andy Lutomirski
      • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
        • Re: [PATCH] proc: allow killing processes via file descriptors, Andy Lutomirski
          • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
            • Re: [PATCH] proc: allow killing processes via file descriptors, Andy Lutomirski
              • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
                • Re: [PATCH] proc: allow killing processes via file descriptors, Eric W. Biederman
                  • Re: [PATCH] proc: allow killing processes via file descriptors, Andy Lutomirski
                  • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
          • Re: [PATCH] proc: allow killing processes via file descriptors, Randy Dunlap
            • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
              • Re: [PATCH] proc: allow killing processes via file descriptors, Andy Lutomirski
                • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
                  • Re: [PATCH] proc: allow killing processes via file descriptors, Andy Lutomirski
                    • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
                      • Re: [PATCH] proc: allow killing processes via file descriptors, Andy Lutomirski
                        • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
                          • Re: [PATCH] proc: allow killing processes via file descriptors, Aleksa Sarai
                            • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
                              • Re: [PATCH] proc: allow killing processes via file descriptors, Christian Brauner
                                • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
                              • Re: [PATCH] proc: allow killing processes via file descriptors, Andy Lutomirski
                                • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
                                • Re: [PATCH] proc: allow killing processes via file descriptors, Andy Lutomirski
                                • Re: [PATCH] proc: allow killing processes via file descriptors, Christian Brauner
                                • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
                                • Re: [PATCH] proc: allow killing processes via file descriptors, Christian Brauner
                                • Re: [PATCH] proc: allow killing processes via file descriptors, Christian Brauner
                                • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
                                • Re: [PATCH] proc: allow killing processes via file descriptors, Christian Brauner
                              • Re: [PATCH] proc: allow killing processes via file descriptors, Aleksa Sarai
                                • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
                                • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
                        • Re: [PATCH] proc: allow killing processes via file descriptors, Dmitry Safonov
                          • Re: [PATCH] proc: allow killing processes via file descriptors (Larger pids), Eric W. Biederman
                          • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
                            • Re: [PATCH] proc: allow killing processes via file descriptors, Aleksa Sarai
                    • Re: [PATCH] proc: allow killing processes via file descriptors, Al Viro
                      • Re: [PATCH] proc: allow killing processes via file descriptors, Andy Lutomirski
      • Re: [PATCH] proc: allow killing processes via file descriptors, Christian Brauner
        • Re: [PATCH] proc: allow killing processes via file descriptors, Andy Lutomirski
        • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
          • Re: [PATCH] proc: allow killing processes via file descriptors, Andy Lutomirski
            • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
          • Re: [PATCH] proc: allow killing processes via file descriptors, Christian Brauner
          • Re: [PATCH] proc: allow killing processes via file descriptors, Aleksa Sarai
            • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
  • Re: [PATCH] proc: allow killing processes via file descriptors, Daniel Colascione
  • Re: [PATCH] proc: allow killing processes via file descriptors, kbuild test robot
  • RE: [PATCH] proc: allow killing processes via file descriptors, David Laight
  • Re: [PATCH] proc: allow killing processes via file descriptors, Dave Martin
• [PATCH 0/3] Fix unsafe BPF_PROG_TEST_RUN interface, Lorenz Bauer
  • [PATCH 2/3] libbpf: require size hint in bpf_prog_test_run, Lorenz Bauer
    • Re: [PATCH 2/3] libbpf: require size hint in bpf_prog_test_run, Y Song
  • [PATCH 3/3] selftests: add a test for bpf_prog_test_run output size, Lorenz Bauer
    • Re: [PATCH 3/3] selftests: add a test for bpf_prog_test_run output size, Y Song
      • Re: [PATCH 3/3] selftests: add a test for bpf_prog_test_run output size, Lorenz Bauer
        • Re: [PATCH 3/3] selftests: add a test for bpf_prog_test_run output size, Y Song
  • [PATCH 1/3] bpf: respect size hint to BPF_PROG_TEST_RUN if present, Lorenz Bauer
    • Re: [PATCH 1/3] bpf: respect size hint to BPF_PROG_TEST_RUN if present, Y Song
  • Re: [PATCH 0/3] Fix unsafe BPF_PROG_TEST_RUN interface, Y Song
    • Re: [PATCH 0/3] Fix unsafe BPF_PROG_TEST_RUN interface, Lorenz Bauer
      • Re: [PATCH 0/3] Fix unsafe BPF_PROG_TEST_RUN interface, Daniel Borkmann
  • [PATCH v2 0/4] Fix unsafe BPF_PROG_TEST_RUN interface, Lorenz Bauer
    • [PATCH v2 3/4] libbpf: require size hint in bpf_prog_test_run, Lorenz Bauer
      • Re: [PATCH v2 3/4] libbpf: require size hint in bpf_prog_test_run, Alexei Starovoitov
        • Re: [PATCH v2 3/4] libbpf: require size hint in bpf_prog_test_run, Lorenz Bauer
          • Re: [PATCH v2 3/4] libbpf: require size hint in bpf_prog_test_run, Alexei Starovoitov
    • [PATCH v2 1/4] bpf: respect size hint to BPF_PROG_TEST_RUN if present, Lorenz Bauer
    • [PATCH v2 2/4] tools: sync uapi/linux/bpf.h, Lorenz Bauer
    • [PATCH v2 4/4] selftests: add a test for bpf_prog_test_run output size, Lorenz Bauer
    • Re: [PATCH v2 0/4] Fix unsafe BPF_PROG_TEST_RUN interface, Y Song
  • [PATCH v3 0/4] Fix unsafe BPF_PROG_TEST_RUN interface, Lorenz Bauer
    • [PATCH v3 1/4] bpf: respect size hint to BPF_PROG_TEST_RUN if present, Lorenz Bauer
    • [PATCH v3 2/4] tools: sync uapi/linux/bpf.h, Lorenz Bauer
    • [PATCH v3 3/4] libbpf: add bpf_prog_test_run_xattr, Lorenz Bauer
      • Re: [PATCH v3 3/4] libbpf: add bpf_prog_test_run_xattr, Daniel Borkmann
        • Re: [PATCH v3 3/4] libbpf: add bpf_prog_test_run_xattr, Alexei Starovoitov
          • Re: [PATCH v3 3/4] libbpf: add bpf_prog_test_run_xattr, Lorenz Bauer
            • Re: [PATCH v3 3/4] libbpf: add bpf_prog_test_run_xattr, Daniel Borkmann
            • Re: [PATCH v3 3/4] libbpf: add bpf_prog_test_run_xattr, Alexei Starovoitov
              • Re: [PATCH v3 3/4] libbpf: add bpf_prog_test_run_xattr, Lorenz Bauer
    • [PATCH v3 4/4] selftests: add a test for bpf_prog_test_run_xattr, Lorenz Bauer
  • [PATCH v4 0/4] Fix unsafe BPF_PROG_TEST_RUN interface, Lorenz Bauer