[PATCH 6.6.y 0/8] can: bcm: backport of 8 patches that failed to apply to 6.6-stable

[PATCH 6.6.y 0/8] can: bcm: backport of 8 patches that failed to apply to 6.6-stable

[Oliver Hartkopp]

This resubmits "can: bcm: add locking when updating filter and timer
values" (commit 749179c2e25b95d22499ed29096b3e02d6dfd2b4 upstream),
which failed to apply to the 6.6-stable tree, together with 7 further
bcm.c patches from the same upstream series that build on it and
would otherwise fail for the same reason.

This assumes the 3 already-queued bcm.c patches for 6.6-stable
("can: bcm: defer rx_op deallocation to workqueue to fix thrtimer
UAF", "can: bcm: fix lockless bound/ifindex race and silent RX_SETUP
failure", "can: bcm: add missing rcu list annotations and
operations") have landed by the time this is applied. If not, please
let me know and I will rebase.

Oliver Hartkopp (8):
  can: bcm: add locking when updating filter and timer values
  can: bcm: fix CAN frame rx/tx statistics
  can: bcm: extend bcm_tx_lock usage for data and timer updates
  can: bcm: validate frame length in bcm_rx_setup() for RTR replies
  can: bcm: add missing device refcount for CAN filter removal
  can: bcm: fix stale rx/tx ops after device removal
  can: bcm: fix data race on rx_stamp/rx_ifindex in bcm_rx_handler()
  can: bcm: track a single source interface for ANYDEV timeout/throttle
    ops

 net/can/bcm.c | 520 +++++++++++++++++++++++++++++++++++++++++++---------------
 1 file changed, 391 insertions(+), 129 deletions(-)

-- 
2.43.0