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

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

[Oliver Hartkopp]

This resubmits "can: bcm: add locking when updating filter and timer
values" (commit 749179c2e25b95d22499ed29096b3e02d6dfd2b4 upstream),
which failed to apply to the 5.10-stable tree, together with 8
further bcm.c patches from the same upstream series that build on it
and would otherwise fail for the same reason. This is the full set
of 11 upstream bcm.c patches from 7.2-rc3 minus the 2 already queued
by the normal stable process for 5.10 ("can: bcm: fix lockless
bound/ifindex race and silent RX_SETUP failure", "can: bcm: add
missing rcu list annotations and operations").

This assumes the 2 already-queued bcm.c patches for 5.10-stable have
landed by the time this is applied. If not, please let me know and I
will rebase.

Lee Jones (1):
  can: bcm: defer rx_op deallocation to workqueue to fix thrtimer UAF

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 | 558 ++++++++++++++++++++++++++++++++++++++++++++--------------
 1 file changed, 425 insertions(+), 133 deletions(-)

-- 
2.43.0