aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/drivers/block/rnull/ssh:/git@git.zx2c4.com/git:/git.zx2c4.com
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2026-05-27 17:23:07 -0700
committerJakub Kicinski <kuba@kernel.org>2026-05-27 17:23:07 -0700
commitce1e33020a5f365823e9a0bfd18d6b3f20e206c6 (patch)
tree5f0a8a122f3365db7a86d97c1fb79f9f2b470b92 /drivers/block/rnull/ssh:/git@git.zx2c4.com/git:/git.zx2c4.com
parentbonding: refuse to enslave CAN devices (diff)
parentselftests: rtnetlink: Add bridge promiscuity tests (diff)
Merge branch 'bridge-fix-sleep-in-atomic-context'
Ido Schimmel says: ==================== bridge: Fix sleep in atomic context Under certain circumstances the bridge driver can call dev_set_promiscuity() while holding the bridge spin lock. This is a problem as dev_set_promiscuity() might sleep. Patches #1-#2 fix the problem in the netlink and sysfs configuration paths by only taking the lock where it is actually needed, thereby avoiding calling dev_set_promiscuity() from an atomic context. Patch #3 adds test cases for both configuration paths in rtnetlink.sh which already includes test cases for similar issues. Note that dev_set_promiscuity() can sleep either when it takes the net device mutex or when calling netif_rx_mode_sync(). I encountered the problem with the latter, but blamed the former since it came earlier. ==================== Link: https://patch.msgid.link/20260526064818.272516-1-idosch@nvidia.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'drivers/block/rnull/ssh:/git@git.zx2c4.com/git:/git.zx2c4.com')
0 files changed, 0 insertions, 0 deletions