user/sven/linux.git/include/net, branch next/masterLinux Kernel
https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=next%2Fmaster2026-04-09T13:23:58ZMerge branch 'for-next' of https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git2026-04-09T13:23:58ZMark Brownbroonie@kernel.org2026-04-09T13:23:58Zurn:sha1:335676461492f6444fd4aa69be187cefd04b08a2Merge branch 'master' of https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git2026-04-09T13:23:57ZMark Brownbroonie@kernel.org2026-04-09T13:23:57Zurn:sha1:dbec2ec7447fccf5c21ec798c7f2f58165da6c00
# Conflicts:
# net/bluetooth/l2cap_core.c
Merge branch 'main' of https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git2026-04-09T13:23:45ZMark Brownbroonie@kernel.org2026-04-09T13:23:40Zurn:sha1:9bbe869aca240d1295448d785064234713a18317Merge branch 'for-next' of https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git2026-04-09T13:23:36ZMark Brownbroonie@kernel.org2026-04-09T13:23:36Zurn:sha1:dcf7b312fae53ceb54bec05639b79491dd481543Merge branch 'fs-next' of linux-next2026-04-09T13:09:24ZMark Brownbroonie@kernel.org2026-04-09T13:09:23Zurn:sha1:85315ec393d8fe7bd0e9543d18cbc3f4ae61b01dMerge branch 'mm-stable' of https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm2026-04-09T12:55:26ZMark Brownbroonie@kernel.org2026-04-09T12:55:26Zurn:sha1:e98894f89da72f392141d9eecf1c7a8f13faa67fnext-20260408/vfs-brauner2026-04-09T12:12:02ZMark Brownbroonie@kernel.org2026-04-09T12:12:00Zurn:sha1:2481f4766702d5ef20bf80fe02add82d27278ea4devlink: Add port-level resource registration infrastructure2026-04-09T02:55:38ZOr Har-Toovohartoov@nvidia.com2026-04-07T19:40:57Zurn:sha1:6f38acfed5edb398201d9ff127919745cbb331a1
The current devlink resource infrastructure supports only device-level
resources. Some hardware resources are associated with specific ports
rather than the entire device, and today we have no way to show resource
per-port.
Add support for registering resources at the port level.
Signed-off-by: Or Har-Toov <ohartoov@nvidia.com>
Reviewed-by: Shay Drori <shayd@nvidia.com>
Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
Link: https://patch.msgid.link/20260407194107.148063-3-tariqt@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
devlink: Refactor resource functions to be generic2026-04-09T02:55:38ZOr Har-Toovohartoov@nvidia.com2026-04-07T19:40:56Zurn:sha1:7be3163c49b24bf923d32f333096963159e03a14
Currently the resource functions take devlink pointer as parameter
and take the resource list from there.
Allow resource functions to work with other resource lists that will
be added in next patches and not only with the devlink's resource list.
Signed-off-by: Or Har-Toov <ohartoov@nvidia.com>
Reviewed-by: Shay Drori <shayd@nvidia.com>
Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
Link: https://patch.msgid.link/20260407194107.148063-2-tariqt@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
net: dropreason: add MACVLAN_BROADCAST_BACKLOG and IPVLAN_MULTICAST_BACKLOG2026-04-09T02:19:18ZEric Dumazetedumazet@google.com2026-04-07T15:07:10Zurn:sha1:202ab599413c9a66e3e4449886b85c7b21314d50
ipvlan and macvlan use queues to process broadcast/multicast packets
from a work queue.
Under attack these queues can drop packets.
Add MACVLAN_BROADCAST_BACKLOG drop_reason for macvlan broadcast queue.
Add IPVLAN_MULTICAST_BACKLOG drop_reason for ipvlan multicast queue.
Use different reasons as some deployments use both ipvlan and macvlan.
Also change ipvlan_rcv_frame() to use SKB_DROP_REASON_DEV_READY
when the device is not UP.
Signed-off-by: Eric Dumazet <edumazet@google.com>
Link: https://patch.msgid.link/20260407150710.1640747-1-edumazet@google.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>