linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
 messages from 2019-09-20 16:29:51 to 2019-10-08 10:30:35 UTC [more...]

[RFC][PATCH] sysctl: Remove the sysctl system call
 2019-10-08 10:30 UTC  (12+ messages)
      ` [REPOST][RFC][PATCH] "
      ` vger mail woes? (was: Re: [RFC][PATCH] sysctl: Remove the sysctl system call)

[PATCH RFC 0/3] document openat2(2) patch series
 2019-10-08  1:33 UTC  (8+ messages)
` [PATCH RFC 1/3] symlink.7: document magic-links more completely
` [PATCH RFC 2/3] open.2: add O_EMPTYPATH documentation
` [PATCH RFC 3/3] openat2.2: document new openat2(2) syscall
` [PATCH RFC 3/3] openat2.2: document new syscall

[PATCH bpf-next] bpf, capabilities: introduce CAP_BPF
 2019-10-04 19:56 UTC  (22+ messages)
                                ` trace_printk issue. Was: "

[PATCH] io_uring: use __kernel_timespec in timeout ABI
 2019-10-01 18:08 UTC  (9+ messages)

[PATCH v4 0/4] lib: introduce copy_struct_from_user() helper
 2019-10-01 16:28 UTC  (12+ messages)
` [PATCH v4 1/4] "
` [PATCH v4 2/4] clone3: switch to copy_struct_from_user()
` [PATCH v4 3/4] sched_setattr: "
` [PATCH v4 4/4] perf_event_open: "

[PATCH -next] treewide: remove unused argument in lock_release()
 2019-10-01 12:46 UTC  (3+ messages)

[PATCH v13 0/9] namei: openat2(2) path resolution restrictions
 2019-10-01  5:06 UTC  (16+ messages)
` [PATCH v13 1/9] namei: obey trailing magic-link DAC permissions
` [PATCH v13 2/9] procfs: switch magic-link modes to be more sane
` [PATCH v13 3/9] open: O_EMPTYPATH: procfs-less file descriptor re-opening
` [PATCH v13 4/9] namei: O_BENEATH-style path resolution flags
` [PATCH v13 5/9] namei: LOOKUP_IN_ROOT: chroot-like path resolution
` [PATCH v13 6/9] namei: permit ".." resolution with LOOKUP_{IN_ROOT, BENEATH}
` [PATCH v13 7/9] open: openat2(2) syscall
` [PATCH v13 8/9] selftests: add openat2(2) selftests
` [PATCH v13 9/9] Documentation: update path-lookup to mention trailing magic-links

[PATCH RESEND v3 0/4] lib: introduce copy_struct_from_user() helper
 2019-10-01  0:40 UTC  (11+ messages)
` [PATCH RESEND v3 1/4] "
` [PATCH RESEND v3 2/4] clone3: switch to copy_struct_from_user()
` [PATCH RESEND v3 3/4] sched_setattr: "
` [PATCH RESEND v3 4/4] perf_event_open: "

[PATCH v3 0/4] lib: introduce copy_struct_from_user() helper
 2019-09-30 18:28 UTC  (5+ messages)
` [PATCH v3 1/4] "
` [PATCH v3 2/4] clone3: switch to copy_struct_from_user()
` [PATCH v3 3/4] sched_setattr: "
` [PATCH v3 4/4] perf_event_open: "

[PATCH RFC v4 1/1] random: WARN on large getrandom() waits and introduce getrandom2()
 2019-09-28  9:30 UTC  (30+ messages)
                  ` [PATCH v5 0/1] random: getrandom(2): warn on large CRNG waits, introduce new flags
                    ` [PATCH v5 1/1] "

[PATCH ghak90 V7 00/21] audit: implement container identifier
 2019-09-27 12:51 UTC  (5+ messages)
` [PATCH ghak90 V7 04/21] audit: convert to contid list to check for orch/engine ownership
` [PATCH ghak90 V7 06/21] audit: contid limit of 32k imposed to avoid DoS

[PATCH v2 0/4] lib: introduce copy_struct_from_user() helper
 2019-09-27  8:20 UTC  (11+ messages)
` [PATCH v2 1/4] "
` [PATCH v2 2/4] clone3: switch to copy_struct_from_user()
` [PATCH v2 3/4] sched_setattr: "
` [PATCH v2 4/4] perf_event_open: "

[RFC PATCH 0/3] fs: interface for directly writing encoded (e.g., compressed) data
 2019-09-26 17:46 UTC  (17+ messages)
` [RFC PATCH 2/3] fs: add RWF_ENCODED for writing compressed data
              ` [RFC PATCH 2/3] "

[PATCH v2 0/7] Rework random blocking
 2019-09-26  1:09 UTC  (4+ messages)
` [PATCH v2 7/7] random: Remove kernel.random.read_wakeup_threshold

[PATCH v1 0/4] lib: introduce copy_struct_from_user() helper
 2019-09-25 20:47 UTC  (20+ messages)
` [PATCH v1 1/4] "
` [PATCH v1 2/4] clone3: switch to copy_struct_from_user()
` [PATCH v1 3/4] sched_setattr: "
` [PATCH v1 4/4] perf_event_open: "

For review: pidfd_send_signal(2) manual page
 2019-09-25 14:29 UTC  (23+ messages)

For review: pidfd_open(2) manual page
 2019-09-24  7:38 UTC  (12+ messages)


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).