From: Nix <nix@esperi.org.uk>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Keeping network device renaming working in the presence of netconsole?
Date: Fri, 16 Oct 2009 20:43:29 +0100 [thread overview]
Message-ID: <87zl7rp1jy.fsf@spindle.srvr.nix> (raw)
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.
next reply other threads:[~2009-10-16 19:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 19:43 Nix [this message]
2009-10-16 19:57 ` Matt Mackall
2009-10-17 11:08 ` Nix
2009-10-20 18:54 ` [PATCH] Allow renaming of network interfaces that are up Nix
2009-10-21 0:39 ` David Miller
2009-10-21 1:38 ` Stephen Hemminger
2009-10-21 6:50 ` Nix
2009-10-23 19:50 ` [PATCH] Make it clear how to rename netconsole-used network interfaces Nix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zl7rp1jy.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®