From: Stephen Hemminger <shemminger@vyatta.com>
To: emil.s.tantilov@intel.com
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6
Date: Mon, 5 Apr 2010 21:39:10 -0700 [thread overview]
Message-ID: <20100405213910.2cbb75b9@nehalam> (raw)
In-Reply-To: <20100405.165317.89399272.davem@davemloft.net>
I can not reproduce this with current net-next and e1000e.
Please recheck that you are running the right code.
# ip addr show dev eth3
6: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:15:17:c3:a9:fb brd ff:ff:ff:ff:ff:ff
inet6 2001:db8:0:f101::1/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::215:17ff:fec3:a9fb/64 scope link
valid_lft forever preferred_lft forever
# ip addr show dev eth3
6: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:15:17:c3:a9:fb brd ff:ff:ff:ff:ff:ff
inet 192.168.1.12/24 brd 192.168.1.255 scope global eth3
inet6 2001:db8:0:f101::1/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::215:17ff:fec3:a9fb/64 scope link
valid_lft forever preferred_lft forever
# ethtool -t eth3
The test result is PASS
The test extra info:
Register test (offline) 0
Eeprom test (offline) 0
Interrupt test (offline) 0
Loopback test (offline) 0
Link test (on/offline) 0
No failures, no backtrace, nothing?
$ git log net/ipv6/addrconf.c
commit 4b97efdf392563bf03b4917a0b5add2df65de39a
Author: Patrick McHardy <kaber@trash.net>
Date: Fri Mar 26 20:27:49 2010 -0700
net: fix netlink address dumping in IPv4/IPv6
When a dump is interrupted at the last device in a hash chain and
then continued, "idx" won't get incremented past s_idx, so s_ip_idx
is not reset when moving on to the next device. This means of all
following devices only the last n - s_ip_idx addresses are dumped.
Tested-by: Pawel Staszewski <pstaszewski@itcare.pl>
Signed-off-by: Patrick McHardy <kaber@trash.net>
commit b79d1d54cf0672f764402fe4711ef5306f917bd3
Author: David S. Miller <davem@davemloft.net>
Date: Thu Mar 25 21:39:21 2010 -0700
ipv6: Fix result generation in ipv6_get_ifaddr().
Finishing naturally from hlist_for_each_entry(x, ...) does not result
in 'x' being NULL.
Signed-off-by: David S. Miller <davem@davemloft.net>
commit b54c9b98bbfb4836b1f7441c5a9db24affd3c2e9
Author: David S. Miller <davem@davemloft.net>
Date: Thu Mar 25 21:25:30 2010 -0700
ipv6: Preserve pervious behavior in ipv6_link_dev_addr().
Use list_add_tail() to get the behavior we had before
the list_head conversion for ipv6 address lists.
Signed-off-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2010-04-06 4:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 18:28 net-next: 2.6.34-rc1 regression: panic when running diagnostic on interface with IPv6 Tantilov, Emil S
2010-03-24 6:33 ` David Miller
2010-04-05 23:03 ` Tantilov, Emil S
2010-04-05 23:12 ` David Miller
2010-04-05 23:50 ` Tantilov, Emil S
2010-04-05 23:53 ` David Miller
2010-04-06 4:39 ` Stephen Hemminger [this message]
2010-04-09 0:54 ` Stephen Hemminger
2010-04-09 8:19 ` Tantilov, Emil S
2010-04-09 15:07 ` Stephen Hemminger
2010-04-09 17:50 ` Tantilov, Emil S
2010-04-12 4:49 ` Stephen Hemminger
2010-04-09 22:19 ` Stephen Hemminger
2010-04-09 23:00 ` Tantilov, Emil S
2010-04-10 2:21 ` Stephen Hemminger
2010-04-06 2:15 ` Stephen Hemminger
2010-04-06 2:37 ` Tantilov, Emil S
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=20100405213910.2cbb75b9@nehalam \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=emil.s.tantilov@intel.com \
--cc=netdev@vger.kernel.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).