From: David Ahern <dsahern@gmail.com>
To: syzbot <syzbot+2add39b05179b31f912f@syzkaller.appspotmail.com>,
christian.brauner@ubuntu.com, davem@davemloft.net, fw@strlen.de,
jbenc@redhat.com, ktkhai@virtuozzo.com,
linux-kernel@vger.kernel.org, lucien.xin@gmail.com,
mschiffer@universe-factory.net, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, vyasevich@gmail.com
Subject: Re: WARNING: suspicious RCU usage in fib6_info_alloc
Date: Wed, 18 Apr 2018 15:04:22 -0600 [thread overview]
Message-ID: <3096e146-ee1d-d3f8-e900-8aa70cb54d00@gmail.com> (raw)
In-Reply-To: <0000000000004366bc056a25c4f3@google.com>
On 4/18/18 3:02 PM, syzbot wrote:
> stack backtrace:
> CPU: 1 PID: 25 Comm: kworker/1:1 Not tainted 4.16.0+ #5
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> Workqueue: ipv6_addrconf addrconf_dad_work
> Call Trace:
> __dump_stack lib/dump_stack.c:77 [inline]
> dump_stack+0x1b9/0x294 lib/dump_stack.c:113
> lockdep_rcu_suspicious+0x14a/0x153 kernel/locking/lockdep.c:4592
> ___might_sleep+0x2e7/0x320 kernel/sched/core.c:6153
> __might_sleep+0x95/0x190 kernel/sched/core.c:6141
> slab_pre_alloc_hook mm/slab.h:421 [inline]
> slab_alloc mm/slab.c:3378 [inline]
> kmem_cache_alloc_trace+0x2bc/0x780 mm/slab.c:3618
> kmalloc include/linux/slab.h:512 [inline]
> kzalloc include/linux/slab.h:701 [inline]
> fib6_info_alloc+0xbb/0x280 net/ipv6/ip6_fib.c:152
> ip6_route_info_create+0x7bf/0x3240 net/ipv6/route.c:2891
> ip6_route_add+0x23/0xb0 net/ipv6/route.c:3030
> addrconf_prefix_route.isra.47+0x4f7/0x6f0 net/ipv6/addrconf.c:2347
> __ipv6_ifa_notify+0x591/0xa00 net/ipv6/addrconf.c:5620
Eric is faster than the robot ;-)
Patch is queued up; will send later today.
next prev parent reply other threads:[~2018-04-18 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 21:02 WARNING: suspicious RCU usage in fib6_info_alloc syzbot
2018-04-18 21:04 ` David Ahern [this message]
2018-04-18 21:16 ` Eric Dumazet
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=3096e146-ee1d-d3f8-e900-8aa70cb54d00@gmail.com \
--to=dsahern@gmail.com \
--cc=christian.brauner@ubuntu.com \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=jbenc@redhat.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=mschiffer@universe-factory.net \
--cc=netdev@vger.kernel.org \
--cc=syzbot+2add39b05179b31f912f@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vyasevich@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.