From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: xemul@openvz.org, netdev@vger.kernel.org
Subject: Re: [PATCH] veth: prevent oops caused by netdev destructor
Date: Mon, 27 Apr 2009 03:05:15 -0700 (PDT) [thread overview]
Message-ID: <20090427.030515.184629602.davem@davemloft.net> (raw)
In-Reply-To: <20090423214120.22bcc680@nehalam>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Thu, 23 Apr 2009 21:41:20 -0700
> The veth driver will oops if sysfs hooks are open while module is removed.
>
> The net device destructor can not point to code in a module; basically
> there are only two possible safe values: NULL - no destructor, or
> free_netdev - free on last use
Applied.
Please provide a proper signoff next time.
Thanks!
prev parent reply other threads:[~2009-04-27 10:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 4:41 [PATCH] veth: prevent oops caused by netdev destructor Stephen Hemminger
2009-04-27 10:05 ` David Miller [this message]
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=20090427.030515.184629602.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=xemul@openvz.org \
/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;
as well as URLs for NNTP newsgroup(s).