summaryrefslogtreecommitdiff
path: root/drivers/md/raid6test/git@git.tavy.me:linux.git
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2026-04-13 14:56:33 -0700
committerJakub Kicinski <kuba@kernel.org>2026-04-13 14:56:33 -0700
commit2e652049a4db27d052f9c987710920ed328a70e9 (patch)
treef4f61b82c8af8270232cc38c1fc706897748728b /drivers/md/raid6test/git@git.tavy.me:linux.git
parent1b9707e6f1a9d5f9e1b91750f24743108b093e2b (diff)
parent5b75e7d6769557fbee2ae46181deaff0c98ca795 (diff)
Merge branch 'net-move-getsockopt-away-from-__user-buffers'
Breno Leitao says: ==================== net: move .getsockopt away from __user buffers Currently, the .getsockopt callback requires __user pointers: int (*getsockopt)(struct socket *sock, int level, int optname, char __user *optval, int __user *optlen); This prevents kernel callers (io_uring, BPF) from using getsockopt on levels other than SOL_SOCKET, since they pass kernel pointers. Following Linus' suggestion [0], this series introduces sockopt_t, a type-safe wrapper around iov_iter, and a getsockopt_iter callback that works with both user and kernel buffers. AF_PACKET and CAN raw are converted as initial users, with selftests covering the trickiest conversion patterns. [0] https://lore.kernel.org/all/CAHk-=whmzrO-BMU=uSVXbuoLi-3tJsO=0kHj1BCPBE3F2kVhTA@mail.gmail.com/ ==================== Link: https://patch.msgid.link/20260408-getsockopt-v3-0-061bb9cb355d@debian.org Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'drivers/md/raid6test/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions