Orange Pi5 kernel

^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  1) Do the ax25_list_lock, ax25_dev_lock, linkfail_lockreally, ax25_frag_lock and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  2) listen_lock have to be bh-safe?
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  3) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  4) Do the netrom and rose locks have to be bh-safe?
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  5) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  6) A device might be deleted after lookup in the SIOCADDRT ioctl but before it's
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  7) being used.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  8) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  9) Routes to a device being taken down might be deleted by ax25_rt_device_down
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) but added by somebody else before the device has been deleted fully.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) The ax25_rt_find_route synopsys is pervert but I somehow had to deal with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) the race caused by the static variable in it's previous implementation.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) Implement proper socket locking in netrom and rose.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) Check socket locking when ax25_rcv is sending to raw sockets.  In particular
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) ax25_send_to_raw() seems fishy.  Heck - ax25_rcv is fishy.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) Handle XID and TEST frames properly.