Linux API
[Prev Page][Next Page]
- [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>
- Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
- From: Daniel Micay <danielmicay@xxxxxxxxx>
- Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
- From: Jann Horn <jannh@xxxxxxxxxx>
- 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: Kees Cook <keescook@xxxxxxxxxxxx>
- Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
- From: Greg KH <greg@xxxxxxxxx>
- 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: Jann Horn <jannh@xxxxxxxxxx>
- [PATCH] ioctl_getfsmap.2: document the GETFSMAP ioctl
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
- 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: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: new ...at() flag: AT_NO_JUMPS
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Jann Horn <jannh@xxxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- Re: [PATCH RFC v2 4/6] proc: support mounting private procfs instances inside same pid namespace
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- [PATCH v3 2/2] pidns: Expose task pid_ns_for_children to userspace
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- [PATCH v3 1/2] ns: Allow ns_entries to have custom symlink content
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- [PATCH v3 0/2] Expose task pid_ns_for_children to userspace
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Re: error value for "internal error"
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
- Re: [PATCH v3] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: [PATCH] userns,pidns: Verify the userns for new pid namespaces
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: error value for "internal error"
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: [PATCH] security: Use user_namespace::level to avoid redundant iterations in cap_capable()
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Oleg Nesterov <oleg@xxxxxxxxxx>
- Re: [PATCH RFC v2 4/6] proc: support mounting private procfs instances inside same pid namespace
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: [PATCH v3 0/4] Improved seccomp logging
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: [PATCH RFC v2 4/6] proc: support mounting private procfs instances inside same pid namespace
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- error value for "internal error"
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
- Re: [PATCH RFC v2 5/6] proc: instantiate only pids that we can ptrace on 'limit_pids=1' mount option
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- [PATCH] security: Use user_namespace::level to avoid redundant iterations in cap_capable()
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Re: [PATCH] userns,pidns: Verify the userns for new pid namespaces
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- [PATCH v5] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Re: [PATCH] userns,pidns: Verify the userns for new pid namespaces
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Re: [PATCH v3] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Re: [PATCH v3 0/4] Improved seccomp logging
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- How to get an owning userns for a superblock
- From: Andrei Vagin <avagin@xxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Jann Horn <jannh@xxxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: [RFC 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
- From: Christoph Lameter <cl@xxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: [v2] fscrypt: Remove __packed from fscrypt_policy
- From: "Theodore Ts'o" <tytso@xxxxxxx>
- Re: [v2] fscrypt: Move key structure and constants to uapi
- From: "Theodore Ts'o" <tytso@xxxxxxx>
- Re: [PATCH] userns,pidns: Verify the userns for new pid namespaces
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: [PATCH] userns,pidns: Verify the userns for new pid namespaces
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: new ...at() flag: AT_NO_JUMPS
- From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: new ...at() flag: AT_NO_JUMPS
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- new ...at() flag: AT_NO_JUMPS
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH] userns,pidns: Verify the userns for new pid namespaces
- From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
- [PATCH v2 resend] Introduce v3 namespaced file capabilities
- From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
- [PATCH] userns,pidns: Verify the userns for new pid namespaces
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: [PATCH v3] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: [PATCH v2] Introduce v3 namespaced file capabilities
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: [PATCH v4] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: kbuild test robot <lkp@xxxxxxxxx>
- [PATCH v2] Introduce v3 namespaced file capabilities
- From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
- [PATCH v9 3/4] arm/syscalls: Optimize address limit check
- From: Thomas Garnier <thgarnie@xxxxxxxxxx>
- [PATCH v9 4/4] arm64/syscalls: Optimize address limit check
- From: Thomas Garnier <thgarnie@xxxxxxxxxx>
- [PATCH v9 2/4] x86/syscalls: Optimize address limit check
- From: Thomas Garnier <thgarnie@xxxxxxxxxx>
- [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode
- From: Thomas Garnier <thgarnie@xxxxxxxxxx>
- [PATCH v4] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Re: [PATCH v3] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Re: [PATCH v8 1/4] syscalls: Verify address limit before returning to user-mode
- From: Ingo Molnar <mingo@xxxxxxxxxx>
- Re: [PATCH v8 1/4] syscalls: Verify address limit before returning to user-mode
- From: Ingo Molnar <mingo@xxxxxxxxxx>
- [PATCH] mnt: allow to add a mount into an existing group
- From: Andrei Vagin <avagin@xxxxxxxxxx>
- Re: [PATCH v3 0/4] Improved seccomp logging
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- Re: [PATCH v3 0/4] Improved seccomp logging
- From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
- Re: [PATCH] Introduce v3 namespaced file capabilities
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: [PATCH] Introduce v3 namespaced file capabilities
- From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: [PATCH] Introduce v3 namespaced file capabilities
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Oleg Nesterov <oleg@xxxxxxxxxx>
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Oleg Nesterov <oleg@xxxxxxxxxx>
- Re: [PATCH v3] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Oleg Nesterov <oleg@xxxxxxxxxx>
- Re: [PATCH v3] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Re: [PATCH v3] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- [PATCH v8 1/4] syscalls: Verify address limit before returning to user-mode
- From: Thomas Garnier <thgarnie@xxxxxxxxxx>
- Re: [PATCH v8 1/4] syscalls: Verify address limit before returning to user-mode
- From: Thomas Garnier <thgarnie@xxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- [PATCH v3] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Re: [PATCH v2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
- [PATCH] statx: correct error handling of NULL pathname
- From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
- Re: [PATCH] statx: Kill fd-with-NULL-path support in favour of AT_EMPTY_PATH
- From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
- [PATCH v2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Cgroups, burst
- From: Kamil Kamiński <kwb.kot@xxxxxxxxx>
- Re: [PATCH v8 1/4] syscalls: Verify address limit before returning to user-mode
- From: Ingo Molnar <mingo@xxxxxxxxxx>
- Re: [PATCH] uapi: change the type of struct statx_timestamp.tv_nsec to unsigned
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
- Re: [PATCH RFC v2 4/6] proc: support mounting private procfs instances inside same pid namespace
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: [PATCH RFC v2 5/6] proc: instantiate only pids that we can ptrace on 'limit_pids=1' mount option
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: [PATCH] statx: Kill fd-with-NULL-path support in favour of AT_EMPTY_PATH
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- [PATCH] statx: Kill fd-with-NULL-path support in favour of AT_EMPTY_PATH
- From: David Howells <dhowells@xxxxxxxxxx>
- Re: Revised statx(2) man page for review [and AT_EMPTY_PATH question]
- From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
- [PATCH v8 2/4] x86/syscalls: Optimize address limit check
- From: Thomas Garnier <thgarnie@xxxxxxxxxx>
- [PATCH v8 3/4] arm/syscalls: Optimize address limit check
- From: Thomas Garnier <thgarnie@xxxxxxxxxx>
- [PATCH v8 4/4] arm64/syscalls: Optimize address limit check
- From: Thomas Garnier <thgarnie@xxxxxxxxxx>
- [PATCH v8 1/4] syscalls: Verify address limit before returning to user-mode
- From: Thomas Garnier <thgarnie@xxxxxxxxxx>
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Oleg Nesterov <oleg@xxxxxxxxxx>
- Re: Revised statx(2) man page for review [and AT_EMPTY_PATH question]
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Re: Revised statx(2) man page for review [and AT_EMPTY_PATH question]
- From: David Howells <dhowells@xxxxxxxxxx>
- Re: [PATCH v7 1/4] syscalls: Restore address limit after a syscall
- From: Thomas Garnier <thgarnie@xxxxxxxxxx>
- [PATCH] uapi: change the type of struct statx_timestamp.tv_nsec to unsigned
- From: David Howells <dhowells@xxxxxxxxxx>
- Re: Revised statx(2) man page for review [and AT_EMPTY_PATH question]
- From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
- Re: Revised statx(2) man page for review [and AT_EMPTY_PATH question]
- From: David Howells <dhowells@xxxxxxxxxx>
- [PATCH v2] uapi: change the type of struct statx_timestamp.tv_nsec to unsigned
- From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
- Re: [PATCH] uapi: remove false assertion that statx_timestamp.tv_nsec can be negative
- From: David Howells <dhowells@xxxxxxxxxx>
- Re: Revised statx(2) man page for review
- From: "G. Branden Robinson" <g.branden.robinson@xxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- Re: [PATCH v7 1/4] syscalls: Restore address limit after a syscall
- From: Ingo Molnar <mingo@xxxxxxxxxx>
- Re: [RFC 1/6] mm, page_alloc: fix more premature OOM due to race with cpuset update
- From: Vlastimil Babka <vbabka@xxxxxxx>
- Re: Revised statx(2) man page for review
- From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
- Re: Revised statx(2) man page for review
- From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
- Re: Revised statx(2) man page for review
- From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
- Re: Revised statx(2) man page for review
- From: Silvan Jegen <s.jegen@xxxxxxxxx>
- Re: [musl] Re: [PATCH resent] uapi libc compat: allow non-glibc to opt out of uapi definitions
- From: Rich Felker <dalias@xxxxxxxx>
- Re: [PATCH v7 1/4] syscalls: Restore address limit after a syscall
- From: Thomas Garnier <thgarnie@xxxxxxxxxx>
- Re: [PATCH v7 1/4] syscalls: Restore address limit after a syscall
- From: Thomas Garnier <thgarnie@xxxxxxxxxx>
- Re: [PATCH v2] fanotify: don't expose EOPENSTALE to userspace
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH v2] fanotify: don't expose EOPENSTALE to userspace
- From: Amir Goldstein <amir73il@xxxxxxxxx>
- Re: [PATCH v2] fanotify: don't expose EOPENSTALE to userspace
- From: "J . Bruce Fields" <bfields@xxxxxxxxxxxx>
- Re: [PATCH resent] uapi libc compat: allow non-glibc to opt out of uapi definitions
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- Re: [musl] Re: [PATCH resent] uapi libc compat: allow non-glibc to opt out of uapi definitions
- From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
- [PATCH RFC v2 6/6] proc: flush task dcache entries from all procfs instances
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- [PATCH RFC v2 4/6] proc: support mounting private procfs instances inside same pid namespace
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- [PATCH RFC v2 1/6] proc: add proc_fs_info struct to store proc information
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- [PATCH RFC v2 5/6] proc: instantiate only pids that we can ptrace on 'limit_pids=1' mount option
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- [PATCH RFC v2 3/6] proc: add helpers to set and get proc hidepid and gid mount options
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- [PATCH RFC v2 2/6] proc: move /proc/{self|thread-self} dentries to proc_fs_info
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- [PATCH RFC v2 0/6] proc: support private proc instances per pidnamespace
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- Re: [musl] Re: [PATCH resent] uapi libc compat: allow non-glibc to opt out of uapi definitions
- From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
- [PATCH v2] fanotify: don't expose EOPENSTALE to userspace
- From: Amir Goldstein <amir73il@xxxxxxxxx>
- Revised statx(2) man page for review
- From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
- Re: [musl] Re: [PATCH resent] uapi libc compat: allow non-glibc to opt out of uapi definitions
- From: Hauke Mehrtens <hauke@xxxxxxxxxx>
- Re: [musl] Re: [PATCH resent] uapi libc compat: allow non-glibc to opt out of uapi definitions
- From: Hauke Mehrtens <hauke@xxxxxxxxxx>
- Re: [PATCH v7 1/4] syscalls: Restore address limit after a syscall
- From: Ingo Molnar <mingo@xxxxxxxxxx>
- Re: [PATCH v7 1/4] syscalls: Restore address limit after a syscall
- From: Ingo Molnar <mingo@xxxxxxxxxx>
- Re: [PATCH 5/8] nowait aio: return on congested block device
- From: Jens Axboe <axboe@xxxxxxxxx>
- Re: [PATCH v7 1/4] syscalls: Restore address limit after a syscall
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- Re: [PATCH 5/8] nowait aio: return on congested block device
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
- Re: [PATCH 2/2] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
- From: Cyrill Gorcunov <gorcunov@xxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- [patch v4 resend 2/2] kcmp: Add KCMP_EPOLL_TFD mode to compare epoll target files
- From: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
- [patch v4 resend 1/2] procfs: fdinfo -- Extend information about epoll target files
- From: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
- [patch v4 resend 0/2] Extend kcmp for epoll sake
- From: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- Re: fanotify read returns with errno == EOPENSTALE
- From: Marko Rauhamaa <marko.rauhamaa@xxxxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
- Re: [PATCH] Introduce v3 namespaced file capabilities
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- [PATCH] uapi: remove false assertion that statx_timestamp.tv_nsec can be negative
- From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
- Re: [PATCH] Introduce v3 namespaced file capabilities
- From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- Re: fanotify read returns with errno == EOPENSTALE
- From: Amir Goldstein <amir73il@xxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- Re: [PATCH] Introduce v3 namespaced file capabilities
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- Re: [PATCH] Introduce v3 namespaced file capabilities
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: [PATCH] Introduce v3 namespaced file capabilities
- From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
- Re: [PATCH] Introduce v3 namespaced file capabilities
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Re: Formal description of system call interface
- From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
- Re: fanotify read returns with errno == EOPENSTALE
- From: Marko Rauhamaa <marko.rauhamaa@xxxxxxxxxxxx>
- Re: Unchecked flags in statx(2) [Should be fixed before 4.11-final?]
- From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
- Re: [PATCH net-next v8 2/3] Add a eBPF helper function to retrieve socket uid
- From: Mickaël Salaün <mic@xxxxxxxxxxx>
- Re: [kernel-hardening] Re: [PATCH v3 1/2] modules:capabilities: automatic module loading restriction
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- Re: [kernel-hardening] Re: [PATCH v3 1/2] modules:capabilities: automatic module loading restriction
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- [PATCHv5 9/9] x86/mm: Allow to have userspace mappings above 47-bits
- From: "Kirill A. Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
- Re: fanotify read returns with errno == EOPENSTALE
- From: Amir Goldstein <amir73il@xxxxxxxxx>
- Re: [kernel-hardening] Re: [PATCH v3 1/2] modules:capabilities: automatic module loading restriction
- From: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
- Re: fanotify read returns with errno == EOPENSTALE
- From: Jan Kara <jack@xxxxxxx>
- Re: [PATCH 5/8] nowait aio: return on congested block device
- From: Jan Kara <jack@xxxxxxx>
- Re: fanotify read returns with errno == EOPENSTALE
- From: Amir Goldstein <amir73il@xxxxxxxxx>
- Re: [kernel-hardening] Re: [PATCH v3 1/2] modules:capabilities: automatic module loading restriction
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- Re: fanotify read returns with errno == EOPENSTALE
- From: Marko Rauhamaa <marko.rauhamaa@xxxxxxxxxxxx>
- Re: fanotify read returns with errno == EOPENSTALE
- From: Amir Goldstein <amir73il@xxxxxxxxx>
- Re: fanotify read returns with errno == EOPENSTALE
- From: Amir Goldstein <amir73il@xxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: [PATCH v3 1/2] modules:capabilities: automatic module loading restriction
- From: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: kbuild test robot <lkp@xxxxxxxxx>
- Re: [PATCH net-next v6 05/11] seccomp: Split put_seccomp_filter() with put_seccomp()
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- Re: [PATCH net-next v6 09/11] seccomp: Enhance test_harness with an assert step mechanism
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- Re: [PATCH net-next v6 04/11] landlock: Add LSM hooks related to filesystem
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- Re: [kernel-hardening] Re: [PATCH net-next v6 04/11] landlock: Add LSM hooks related to filesystem
- From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Kees Cook <keescook@xxxxxxxxxxxx>
- Re: [PATCH v3 1/2] modules:capabilities: automatic module loading restriction
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Andy Lutomirski <luto@xxxxxxxxxx>
- Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
- [PATCH v3 1/2] modules:capabilities: automatic module loading restriction
- From: Djalal Harouni <tixxdz@xxxxxxxxx>
[Index of Archives]
[Linux USB Devel]
[Video for Linux]
[Linux SCSI]
[Samba]
[Yosemite News]