From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot
<bot+79de6f09efc55fec084b706de3c91e9457433ac5@syzkaller.appspotmail.com>
Cc: David Miller <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
syzkaller-bugs@googlegroups.com,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
dccp@vger.kernel.org, Gerrit Renker <gerrit@erg.abdn.ac.uk>
Subject: Re: suspicious RCU usage at ./include/net/inet_sock.h:LINE
Date: Sun, 5 Nov 2017 11:41:26 +0300 [thread overview]
Message-ID: <CACT4Y+a9jXZS3Ux-KiTPvSa59Fd0uQ7vBYFqyrtmEckEHBg8mg@mail.gmail.com> (raw)
In-Reply-To: <001a1140ad88c4f006055d3836d2@google.com>
On Sun, Nov 5, 2017 at 11:35 AM, syzbot
<bot+79de6f09efc55fec084b706de3c91e9457433ac5@syzkaller.appspotmail.com>
wrote:
> Hello,
>
> syzkaller hit the following crash on
> 5a3517e009e979f21977d362212b7729c5165d92
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is attached.
>
>
>
>
>
> =============================
> WARNING: suspicious RCU usage
> 4.14.0-rc7-next-20171103+ #10 Not tainted
> -----------------------------
> ./include/net/inet_sock.h:136 suspicious rcu_dereference_check() usage!
>
> other info that might help us debug this:
>
>
> rcu_scheduler_active = 2, debug_locks = 1
> 1 lock held by syz-executor0/836:
> #0: (sk_lock-AF_INET6){+.+.}, at: [<ffffffff840fe133>] lock_sock
> include/net/sock.h:1461 [inline]
> #0: (sk_lock-AF_INET6){+.+.}, at: [<ffffffff840fe133>]
> sock_setsockopt+0x163/0x1ae0 net/core/sock.c:715
>
> stack backtrace:
> CPU: 0 PID: 836 Comm: syz-executor0 Not tainted 4.14.0-rc7-next-20171103+
> #10
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
> Call Trace:
> __dump_stack lib/dump_stack.c:17 [inline]
> dump_stack+0x194/0x257 lib/dump_stack.c:53
> lockdep_rcu_suspicious+0x123/0x170 kernel/locking/lockdep.c:4675
> ireq_opt_deref include/net/inet_sock.h:135 [inline]
> inet_csk_route_req+0x82a/0xca0 net/ipv4/inet_connection_sock.c:544
> dccp_v4_send_response+0xa7/0x640 net/dccp/ipv4.c:485
> dccp_v4_conn_request+0x9f4/0x11b0 net/dccp/ipv4.c:633
> dccp_v6_conn_request+0xd30/0x1350 net/dccp/ipv6.c:317
> dccp_rcv_state_process+0x574/0x1620 net/dccp/input.c:612
> dccp_v4_do_rcv+0xeb/0x160 net/dccp/ipv4.c:682
> dccp_v6_do_rcv+0x81a/0x9b0 net/dccp/ipv6.c:578
> sk_backlog_rcv include/net/sock.h:909 [inline]
> __release_sock+0x124/0x360 net/core/sock.c:2264
> release_sock+0xa4/0x2a0 net/core/sock.c:2776
> sock_setsockopt+0x513/0x1ae0 net/core/sock.c:1066
> SYSC_setsockopt net/socket.c:1847 [inline]
> SyS_setsockopt+0x2ff/0x360 net/socket.c:1830
> entry_SYSCALL_64_fastpath+0x1f/0xbe
> RIP: 0033:0x447c89
> RSP: 002b:00007f86cc482bd8 EFLAGS: 00000246 ORIG_RAX: 0000000000000036
> RAX: ffffffffffffffda RBX: 00007f86cc4836cc RCX: 0000000000447c89
> RDX: 000000000000001a RSI: 0000000000000001 RDI: 0000000000000013
> RBP: 0000000000000086 R08: 0000000000000010 R09: 0000000000000000
> R10: 0000000020c3a000 R11: 0000000000000246 R12: 00000000ffffffff
> R13: 00000000000006c0 R14: 00000000006e4760 R15: 00007f86cc483700
>
> =============================
> WARNING: suspicious RCU usage
> 4.14.0-rc7-next-20171103+ #10 Not tainted
> -----------------------------
> ./include/net/inet_sock.h:136 suspicious rcu_dereference_check() usage!
>
> other info that might help us debug this:
>
>
> rcu_scheduler_active = 2, debug_locks = 1
> 1 lock held by syz-executor0/836:
> #0: (sk_lock-AF_INET6){+.+.}, at: [<ffffffff840fe133>] lock_sock
> include/net/sock.h:1461 [inline]
> #0: (sk_lock-AF_INET6){+.+.}, at: [<ffffffff840fe133>]
> sock_setsockopt+0x163/0x1ae0 net/core/sock.c:715
>
> stack backtrace:
> CPU: 0 PID: 836 Comm: syz-executor0 Not tainted 4.14.0-rc7-next-20171103+
> #10
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
> Call Trace:
> __dump_stack lib/dump_stack.c:17 [inline]
> dump_stack+0x194/0x257 lib/dump_stack.c:53
> lockdep_rcu_suspicious+0x123/0x170 kernel/locking/lockdep.c:4675
> ireq_opt_deref include/net/inet_sock.h:135 [inline]
> dccp_v4_send_response+0x4b0/0x640 net/dccp/ipv4.c:496
> dccp_v4_conn_request+0x9f4/0x11b0 net/dccp/ipv4.c:633
> dccp_v6_conn_request+0xd30/0x1350 net/dccp/ipv6.c:317
> dccp_rcv_state_process+0x574/0x1620 net/dccp/input.c:612
> dccp_v4_do_rcv+0xeb/0x160 net/dccp/ipv4.c:682
> dccp_v6_do_rcv+0x81a/0x9b0 net/dccp/ipv6.c:578
> sk_backlog_rcv include/net/sock.h:909 [inline]
> __release_sock+0x124/0x360 net/core/sock.c:2264
> release_sock+0xa4/0x2a0 net/core/sock.c:2776
> sock_setsockopt+0x513/0x1ae0 net/core/sock.c:1066
> SYSC_setsockopt net/socket.c:1847 [inline]
> SyS_setsockopt+0x2ff/0x360 net/socket.c:1830
> entry_SYSCALL_64_fastpath+0x1f/0xbe
> RIP: 0033:0x447c89
> RSP: 002b:00007f86cc482bd8 EFLAGS: 00000246 ORIG_RAX: 0000000000000036
> RAX: ffffffffffffffda RBX: 00007f86cc4836cc RCX: 0000000000447c89
> RDX: 000000000000001a RSI: 0000000000000001 RDI: 0000000000000013
> RBP: 0000000000000086 R08: 0000000000000010 R09: 0000000000000000
> R10: 0000000020c3a000 R11: 0000000000000246 R12: 00000000ffffffff
> R13: 00000000000006c0 R14: 00000000006e4760 R15: 00007f86cc483700
+dccp mailing list
> ---
> This bug is generated by a dumb bot. It may contain errors.
> See https://goo.gl/tpsmEJ for details.
> Direct all questions to syzkaller@googlegroups.com.
> Please credit me with: Reported-by: syzbot <syzkaller@googlegroups.com>
>
> syzbot will keep track of this bug report.
> Once a fix for this bug is committed, please reply to this email with:
> #syz fix: exact-commit-title
> To mark this as a duplicate of another syzbot report, please reply with:
> #syz dup: exact-subject-of-another-report
> If it's a one-off invalid bug report, please reply with:
> #syz invalid
> Note: if the crash happens again, it will cause creation of a new bug
> report.
> Note: all commands must start from beginning of the line.
>
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-bugs/001a1140ad88c4f006055d3836d2%40google.com.
> For more options, visit https://groups.google.com/d/optout.
next parent reply other threads:[~2017-11-05 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a1140ad88c4f006055d3836d2@google.com>
2017-11-05 8:41 ` Dmitry Vyukov [this message]
2017-12-26 1:45 ` suspicious RCU usage at ./include/net/inet_sock.h:LINE syzbot
2018-04-08 19:29 ` Eric Biggers
2018-05-17 16:09 ` Dmitry Vyukov
2019-11-07 13:42 ` syzbot
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=CACT4Y+a9jXZS3Ux-KiTPvSa59Fd0uQ7vBYFqyrtmEckEHBg8mg@mail.gmail.com \
--to=dvyukov@google.com \
--cc=bot+79de6f09efc55fec084b706de3c91e9457433ac5@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dccp@vger.kernel.org \
--cc=gerrit@erg.abdn.ac.uk \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--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).