From: Ferenc Wagner <hidden> Date: 2011-01-03 17:27:30
Hi,
In a running system, I can load the netconsole module, and gather the
messages on the other side all right. Now if I modprobe dummy and rmmod
dummy, the following message gets logged (via netconsole as well):
netconsole: network logging stopped, interface dummy0 unregistered
although I never asked netconsole to log through dummy0. The problem is
fairly obvious in netconsole_netdev_event() and could probably be fixed
with something like the first attached patch. I didn't even compile
tested it, though, because the second attached patch made me realise
that I don't quite understand the bridge logic here. Why should
netconsole stop logging through a bridge device if that loses a slave?
Or do I misunderstand the meaning of NETDEV_BONDING_DESLAVE?
Please Cc me, I'm not subscribed.
--
Thanks,
Feri.
From: Ferenc Wagner <hidden> Date: 2011-01-06 15:47:59
Hi,
I've been running with these two patches for a couple of days now.
I don't understand the bridge case: why should netconsole stop logging
on a bridge device which lost a slave? Or does NETDEV_BONDING_DESLAVE
mean something else?
Anyway, I think the first patch fixes a real bug and the second makes
the kernel message clearer, independently of its cause.
Regards,
Feri.
Ferenc Wagner (2):
netconsole: don't announce stopping if nothing happened
netconsole: clarify stopping message
drivers/net/netconsole.c | 8 +++++---
1 files changed, 5 insertions(+), 3 deletions(-)
From: David Miller <davem@davemloft.net> Date: 2011-01-06 19:30:15
From: Ferenc Wagner <redacted>
Date: Thu, 6 Jan 2011 16:11:18 +0100
Hi,
I've been running with these two patches for a couple of days now.
I don't understand the bridge case: why should netconsole stop logging
on a bridge device which lost a slave? Or does NETDEV_BONDING_DESLAVE
mean something else?
Anyway, I think the first patch fixes a real bug and the second makes
the kernel message clearer, independently of its cause.