Kuniyuki Iwashima c9abdd07f5 mctp: Handle error of rtnl_register_module(). ... [ Upstream commit d51705614f ] 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> Signed-off-by: Sasha Levin <sashal@kernel.org>		2024-10-17 15:11:57 +02:00
..
af_mctp.c	mctp: Handle error of rtnl_register_module().	2024-10-17 15:11:57 +02:00
device.c	mctp: Handle error of rtnl_register_module().	2024-10-17 15:11:57 +02:00
Kconfig	mctp: Add MCTP base	2021-07-29 15:06:49 +01:00
Makefile	mctp: Add neighbour implementation	2021-07-29 15:06:50 +01:00
neigh.c	mctp: Handle error of rtnl_register_module().	2024-10-17 15:11:57 +02:00
route.c	mctp: Handle error of rtnl_register_module().	2024-10-17 15:11:57 +02:00