summaryrefslogtreecommitdiff
path: root/drivers/net
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2026-06-23 19:12:49 -0700
committerJakub Kicinski <kuba@kernel.org>2026-06-23 19:12:50 -0700
commitc79349905706d1a9f5047cda1a155d1870535221 (patch)
tree09fc5778984804445f7653e72c3c1bafedb5fb2c /drivers/net
parent89adcf17ee7a2b7bee584c9c69382118f23dce72 (diff)
parent17dc3b245de45b1f2012e3a48ec51889f544e67b (diff)
downloadlinux-next-c79349905706d1a9f5047cda1a155d1870535221.tar.gz
linux-next-c79349905706d1a9f5047cda1a155d1870535221.zip
Merge branch 'ipv6-fix-error-handling-in-disable_ipv6-sysctl'
Fernando Fernandez Mancera says: ==================== ipv6: fix error handling in disable_ipv6 sysctl While working on a different IPv6 patch series I have spotted multiple minor bugs around sysctl error handling and notifications. In general, they are not serious issues. In addition, there is one more issue in forwarding sysctl as it does not check for CAP_NET_ADMIN for the namespace. I am keeping that patch out of this series and I am aiming it at the net-next tree once it re-opens. During v3, Ido's pointed out that it is unnecessary to reset the position pointer when the return value is negative as at new_sync_write() the ppos is only advanced when ret return value is positive. That means we can get rid of that operation in ipv4/ipv6 sysctls. That is going to be sent to net-next too. ==================== Link: https://patch.msgid.link/20260622130857.5115-1-fmancera@suse.de Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'drivers/net')
0 files changed, 0 insertions, 0 deletions