Message-ID: <001a11479e32f4f8c50561f21514@google.com>
Date:   Thu, 04 Jan 2018 04:01:01 -0800
From:   syzbot <syzbot+777bf170a89e7b326405@...kaller.appspotmail.com>
To:     davem@...emloft.net, herbert@...dor.apana.org.au,
        kuznet@....inr.ac.ru, linux-kernel@...r.kernel.org,
        netdev@...r.kernel.org, steffen.klassert@...unet.com,
        syzkaller-bugs@...glegroups.com, yoshfuji@...ux-ipv6.org
Subject: WARNING in xfrm6_tunnel_net_exit

Hello,

syzkaller hit the following crash on  
00a5ae218d57741088068799b810416ac249a9ce
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.
Unfortunately, I don't have any reproducer for this bug yet.


IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+777bf170a89e7b326405@...kaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for  
details.
If you forward the report, please keep this part and the footer.

The task syz-executor4 (14454) triggered the difference, watch for  
misbehavior.
WARNING: CPU: 0 PID: 294 at net/ipv6/xfrm6_tunnel.c:345  
xfrm6_tunnel_net_exit+0x253/0x460 net/ipv6/xfrm6_tunnel.c:345
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 294 Comm: kworker/u4:4 Not tainted 4.15.0-rc6+ #247
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS  
Google 01/01/2011
Workqueue: netns cleanup_net
Call Trace:
  __dump_stack lib/dump_stack.c:17 [inline]
  dump_stack+0x194/0x257 lib/dump_stack.c:53
  panic+0x1e4/0x41c kernel/panic.c:183
  __warn+0x1dc/0x200 kernel/panic.c:547
  report_bug+0x211/0x2d0 lib/bug.c:184
  fixup_bug.part.11+0x37/0x80 arch/x86/kernel/traps.c:178
  fixup_bug arch/x86/kernel/traps.c:247 [inline]
  do_error_trap+0x2d7/0x3e0 arch/x86/kernel/traps.c:296
  do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:315
  invalid_op+0x22/0x40 arch/x86/entry/entry_64.S:1079
RIP: 0010:xfrm6_tunnel_net_exit+0x253/0x460 net/ipv6/xfrm6_tunnel.c:345
RSP: 0018:ffff8801d920f198 EFLAGS: 00010293
RAX: ffff8801d91f66c0 RBX: ffff8801d4861600 RCX: ffffffff84c41153
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000282
RBP: ffff8801d920f2c0 R08: 0000000000000000 R09: 1ffff1003b241e14
R10: ffff8801d920f068 R11: 0000000000000003 R12: ffffed003b241e3b
R13: ffff8801d920f298 R14: dffffc0000000000 R15: ffff8801d4861e00
  ops_exit_list.isra.6+0xae/0x150 net/core/net_namespace.c:142
  cleanup_net+0x5c7/0xb50 net/core/net_namespace.c:484
  process_one_work+0xbbf/0x1b10 kernel/workqueue.c:2112
  worker_thread+0x223/0x1990 kernel/workqueue.c:2246
  kthread+0x33c/0x400 kernel/kthread.c:238
  ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:524
Dumping ftrace buffer:
    (ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzkaller@...glegroups.com.

syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is  
merged
into any tree, 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 in the email body.

View attachment "config.txt" of type "text/plain" (134059 bytes)

Download attachment "raw.log" of type "application/octet-stream" (1048576 bytes)

Powered by blists - more mailing lists