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: <87zl7rp1jy.fsf@spindle.srvr.nix> Date: Fri, 16 Oct 2009 20:43:29 +0100 From: Nix <nix@...eri.org.uk> To: Matt Mackall <mpm@...enic.com> Cc: linux-kernel@...r.kernel.org Subject: Keeping network device renaming working in the presence of netconsole? So I'm testing suspend/resume and getting a lot of wildly variable panics on resume. I'd like to report them, so I need to capture them somehow. Netconsole looks like just the thing: it even says it's nonintrusive. Unfortunately it intrudes in one very unfortunate way: if netconsole is jabbering out of some network interface, that interface is up, so you can't rename it: and because (to catch early panics) netconsole has to start before userspace kicks up, this means that there is *no* opportunity to rename network interfaces that netconsole is operating over. This breaks userspace more than slightly if you rely on udev's persistent net generator rules to keep network interface names constant, or if you rename the lot to something more memorable than ethN. Any userspace setup of that interface, assignment of additional addresses, routing, MTU setting et al is all toast: and you can't stop using interface renaming unless you like your interfaces to change identities intermittently (but we've had that flamewar). Is there a way to rename interfaces netconsole is working over? Why can't you rename interfaces that are in use anyway? Yes, there's the name_hlist, but that's protected by the dev_base_lock anyway. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists