From: Greg KH <greg@kroah.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: ???????????? <yoshfuji@linux-ipv6.org>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] [PATCH] ipv6: track device renames in snmp6
Date: Thu, 26 Apr 2007 21:16:59 -0700 [thread overview]
Message-ID: <20070427041659.GB4841@kroah.com> (raw)
In-Reply-To: <20070426164247.3b3b2c7a@freekitty>
On Thu, Apr 26, 2007 at 04:42:47PM -0700, Stephen Hemminger wrote:
> When network device's are renamed, the IPV6 snmp6 code
> gets confused. It doesn't track name changes so it will OOPS
> when network device's are removed.
>
> The fix is trivial, just unregister/re-register in notify handler.
>
> Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org>
Which -stable is this for, 2.6.20 or 2.6.21?
thanks,
greg k-h
next prev parent reply other threads:[~2007-04-27 4:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 23:42 [PATCH] ipv6: track device renames in snmp6 Stephen Hemminger
2007-04-27 4:16 ` Greg KH [this message]
2007-04-27 18:17 ` [stable] " Stephen Hemminger
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=20070427041659.GB4841@kroah.com \
--to=greg@kroah.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=stable@kernel.org \
--cc=yoshfuji@linux-ipv6.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).