Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jamie Heilman <jamie@audible.transient.net>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.38-rc1: arp triggers RTNL assertion
Date: Fri, 21 Jan 2011 08:12:26 +0100	[thread overview]
Message-ID: <1295593946.2613.52.camel@edumazet-laptop> (raw)
In-Reply-To: <20110121061758.GA2247@fifty-fifty.audible.transient.net>

Le jeudi 20 janvier 2011 à 22:17 -0800, Jamie Heilman a écrit :
> With 2.6.38-rc1 when I run: arp -Ds 192.168.2.41 eth0 pub
> I see:
> 
> RTNL: assertion failed at net/core/neighbour.c (589)
> Pid: 2330, comm: arp Not tainted 2.6.38-rc1-00132-g8d99641-dirty #1
> Call Trace:
>  [<c11ed339>] ? pneigh_lookup+0xc3/0x168
>  [<c1219f27>] ? arp_req_set+0x86/0x1d5
>  [<c11e74b5>] ? dev_get_by_name_rcu+0x72/0x7f
>  [<c121a1a3>] ? arp_ioctl+0x12d/0x22e
>  [<c121dfeb>] ? inet_ioctl+0x82/0xa7
>  [<c11d8ffc>] ? sock_ioctl+0x1b7/0x1db
>  [<c11d8e45>] ? sock_ioctl+0x0/0x1db
>  [<c108f02f>] ? do_vfs_ioctl+0x47c/0x4c5
>  [<c101803c>] ? do_page_fault+0x315/0x341
>  [<c11daaf3>] ? sys_socket+0x44/0x5a
>  [<c11dab71>] ? sys_socketcall+0x68/0x270
>  [<c108f0ab>] ? sys_ioctl+0x33/0x4b
>  [<c1002897>] ? sysenter_do_call+0x12/0x26
> 
> Figured I'd Cc Eric as this could be related to commit 941666c2,
> "net: RCU conversion of dev_getbyhwaddr() and arp_ioctl()"
> 
> Config attached, just in case (the uncommited change, in the tree this
> kernel was built from, is just Chuck Lever's recent nfs3xdr.c patch).

Thanks for the report, I am looking at this right now.




  reply	other threads:[~2011-01-21  7:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21  6:17 2.6.38-rc1: arp triggers RTNL assertion Jamie Heilman
2011-01-21  7:12 ` Eric Dumazet [this message]
2011-01-21 14:02   ` Richard Cochran
2011-01-21 18:52   ` Eric Dumazet
2011-01-21 21:06     ` David Miller
2011-01-21 22:13       ` Eric Dumazet
2011-01-24 21:11       ` Eric Dumazet
2011-01-24 21:14         ` David Miller

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=1295593946.2613.52.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=jamie@audible.transient.net \
    --cc=linux-kernel@vger.kernel.org \
    --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