[moderation/CI] Re: net: netrom: fix lock order inversion in nr_add_node, nr_del_node and nr_dec_obs

[moderation/CI] Re: net: netrom: fix lock order inversion in nr_add_node, nr_del_node and nr_dec_obs

[syzbot ci]

syzbot ci has tested the following series

[v1] net: netrom: fix lock order inversion in nr_add_node, nr_del_node and nr_dec_obs
https://lore.kernel.org/all/20260406110643.82577-1-mashiro.chen@mailbox.org
* [PATCH net] net: netrom: fix lock order inversion in nr_add_node, nr_del_node and nr_dec_obs

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/54fe750b-7b2a-4915-8b4d-6b7488a3c190

***

kernel build error

tree:      net
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net.git
base:      1caa871bb0615e2b68aa11bb7b453eeac770ea1d
arch:      amd64
compiler:  Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config:    https://ci.syzbot.org/builds/0d6ae9c5-6e6a-4046-a3ab-25c17283d0fd/config

net/netrom/nr_route.c:250:6: error: call to undeclared function 'nr_remove_neigh_locked'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]

***

If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
  Tested-by: syzbot@syzkaller.appspotmail.com

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.

To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).

The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.

The email will later be sent to:
[davem@davemloft.net edumazet@google.com horms@kernel.org kuba@kernel.org linux-hams@vger.kernel.org linux-kernel@vger.kernel.org mashiro.chen@mailbox.org netdev@vger.kernel.org pabeni@redhat.com syzbot@syzkaller.appspotmail.com]

If the report looks fine to you, reply with:
#syz upstream

If the report is a false positive, reply with
#syz invalid