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
| ||
|
Message-ID: <1355580838.2467.39.camel@thor> Date: Sat, 15 Dec 2012 09:13:58 -0500 From: Peter Hurley <peter@...leysoftware.com> To: Neil Horman <nhorman@...driver.com> Cc: Cong Wang <xiyou.wangcong@...il.com>, netdev@...r.kernel.org Subject: Re: netconsole fun On Fri, 2012-12-14 at 09:20 -0500, Neil Horman wrote: > Ah! I'm sorry, I didn't realize this was really about getting netconsole up > early in the boot, rather than just getting it up robustly using the startup > script. Well, it's both but I should have been clearer here. Sorry about that. > If thats the case, then I would recommend that you modify the initramfs > to do something simmilar to the startup script (since thats where the netconsole > module will get loaded anyway). You can write a script there that will let you > specify the destination ip address and figure out the output dev based on the > routing tables. If you're using dracut to build your initramfs, then this > should be pretty straightforward. When I get some more free time I'll experiment with this approach. Just to clarify something from earlier in the discussion: On Thu, 2012-12-13 at 13:08 -0500, Neil Horman wrote: > On Thu, Dec 13, 2012 at 09:49:31AM -0500, Peter Hurley wrote: .... > > There is an unforeseen consequence of the patch: it breaks device > > renaming because the device will already be in use by netconsole. Which > > is the whole problem with userspace device renaming to begin with... > > > That is bad, but see above, the netconsole service can work around this for you, > allowing you to never have to specify a particular device at all. The breakage is a normal consequence of being able to load netconsole before the udev rules that do device renaming. The same thing would happen modifying initramfs. Basically, once netconsole attaches to a device, that device cannot be renamed. Unfortunately, the default udev behavior messes things up further because it will try to do this: eth0->eth1 eth1->eth0 which means neither device will be renamed. Maybe the net core should just implement persistent device names ;) Thanks again for all your time, Peter Hurley -- 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
Powered by blists - more mailing lists