Kuniyuki Iwashima d51705614f mctp: Handle error of rtnl_register_module(). ... Since introduced, mctp has been ignoring the returned value of rtnl_register_module(), which could fail silently. Handling the error allows users to view a module as an all-or-nothing thing in terms of the rtnetlink functionality. This prevents syzkaller from reporting spurious errors from its tests, where OOM often occurs and module is automatically loaded. Let's handle the errors by rtnl_register_many(). Fixes: 583be982d9 ("mctp: Add device handling and netlink interface") Fixes: 831119f887 ("mctp: Add neighbour netlink interface") Fixes: 06d2f4c583 ("mctp: Add netlink route management") Signed-off-by: Kuniyuki Iwashima <kuniyu@amazon.com> Reviewed-by: Jeremy Kerr <jk@codeconstruct.com.au> Signed-off-by: Paolo Abeni <pabeni@redhat.com>		2024-10-10 15:39:35 +02:00
..
test	net: mctp: test: Use correct skb for route input check	2024-08-19 17:48:00 -07:00
af_mctp.c	mctp: Handle error of rtnl_register_module().	2024-10-10 15:39:35 +02:00
device.c	mctp: Handle error of rtnl_register_module().	2024-10-10 15:39:35 +02:00
Kconfig	net: mctp: tests: Test that outgoing skbs have flow data populated	2024-02-22 13:32:55 +01:00
Makefile
neigh.c	mctp: Handle error of rtnl_register_module().	2024-10-10 15:39:35 +02:00
route.c	mctp: Handle error of rtnl_register_module().	2024-10-10 15:39:35 +02:00