netdev - netconsole dumbs the system (in initramfs with bonding and vlan)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 08 Feb 2010 22:01:31 +0100
From:	Ferenc Wagner <wferi@...f.hu>
To:	netdev@...r.kernel.org
Subject: netconsole dumbs the system (in initramfs with bonding and vlan)

Hi,

I set up networking from the initramfs like this:

----------------------------------------
ifup()
{
    ip addr add $2 dev $1
    ip link set up dev $1
    echo "Configured $1 with address $2"
}

BOND=bond0

modprobe bonding
cd /sys/class/net/$BOND/bonding

echo active-backup >mode
echo +eth0 >slaves
echo +eth1 >slaves
echo eth0 >primary
echo +10.0.0.1 >arp_ip_target
echo +10.0.0.2 >arp_ip_target
echo 1000 >arp_interval

vconfig set_name_type VLAN_PLUS_VID_NO_PAD
vconfig add $BOND 39

ifup $BOND 10.0.0.6/24
ifup vlan39 10.253.1.103/24
----------------------------------------

which mostly works, apart from the occasional flood of "bonding: bond0:
doing slave updates when interface is down" messages as detailed in my
previous mail.  However, if I afterwards issue

# modprobe netconsole netconsole=@...0.0.6/eth0,@10.0.0.7/

that kills off the consoles: past kernel messages start pouring over all
consoles, the new network console included, then it suddenly dies off in
the middle, with one more line on the VC than sent to the network.  At
this point, the machine still responds to ping, the keyboard leds work,
but otherwise it's impossible to interact with it.  No SysRq, even.
Being in the initramfs, there are no network services to test.  If I
load netconsole in the running system, there isn't much backlog to pour
out, and the problem doesn't appear.  What could be wrong here?
-- 
Thanks,
Feri.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html