All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+1edeee8da2474fe17a53@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: general protection fault in simple_recursive_removal
Date: Fri, 10 Jan 2020 11:10:09 -0800	[thread overview]
Message-ID: <000000000000d9034c059bcddf3c@google.com> (raw)

Hello,

syzbot found the following crash on:

HEAD commit:    6c09d7db Add linux-next specific files for 20200110
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=157b65c6e00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=246a085809cfc9f7
dashboard link: https://syzkaller.appspot.com/bug?extid=1edeee8da2474fe17a53
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)

Unfortunately, I don't have any reproducer for this crash yet.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+1edeee8da2474fe17a53@syzkaller.appspotmail.com

general protection fault, probably for non-canonical address  
0xdffffc0000000028: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000140-0x0000000000000147]
CPU: 1 PID: 29862 Comm: syz-executor.4 Not tainted  
5.5.0-rc5-next-20200110-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS  
Google 01/01/2011
RIP: 0010:__lock_acquire+0x1254/0x4a00 kernel/locking/lockdep.c:3827
Code: 00 0f 85 96 24 00 00 48 81 c4 f0 00 00 00 5b 41 5c 41 5d 41 5e 41 5f  
5d c3 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00 0f  
85 0b 28 00 00 49 81 3e 20 f9 df 8a 0f 84 5f ee ff
RSP: 0018:ffffc90007ac78d0 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000028 RSI: 0000000000000000 RDI: 0000000000000001
RBP: ffffc90007ac79e8 R08: 0000000000000001 R09: 0000000000000001
R10: fffffbfff1549320 R11: ffff8880375be640 R12: 0000000000000140
R13: 0000000000000000 R14: 0000000000000140 R15: 0000000000000000
FS:  00007f6dc39ee700(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2e625000 CR3: 00000000a8998000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
  lock_acquire+0x190/0x410 kernel/locking/lockdep.c:4484
  down_write+0x93/0x150 kernel/locking/rwsem.c:1534
  inode_lock include/linux/fs.h:791 [inline]
  simple_recursive_removal+0x185/0x720 fs/libfs.c:273
  debugfs_remove fs/debugfs/inode.c:713 [inline]
  debugfs_remove+0x5e/0x80 fs/debugfs/inode.c:707
  blk_trace_free+0x38/0x140 kernel/trace/blktrace.c:311
  do_blk_trace_setup+0x735/0xb50 kernel/trace/blktrace.c:556
  __blk_trace_setup+0xe3/0x190 kernel/trace/blktrace.c:570
  blk_trace_ioctl+0x170/0x300 kernel/trace/blktrace.c:709
  blkdev_ioctl+0xc3/0x670 block/ioctl.c:710
  block_ioctl+0xee/0x130 fs/block_dev.c:1983
  vfs_ioctl fs/ioctl.c:47 [inline]
  ksys_ioctl+0x123/0x180 fs/ioctl.c:760
  __do_sys_ioctl fs/ioctl.c:769 [inline]
  __se_sys_ioctl fs/ioctl.c:767 [inline]
  __x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:767
  do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:294
  entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45af49
Code: ad b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7  
48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff  
ff 0f 83 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f6dc39edc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045af49
RDX: 0000000020000080 RSI: 00000000c0481273 RDI: 000000000000000b
RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f6dc39ee6d4
R13: 00000000004c2acf R14: 00000000004d8f28 R15: 00000000ffffffff
Modules linked in:
---[ end trace 69c29488e75b4707 ]---
RIP: 0010:__lock_acquire+0x1254/0x4a00 kernel/locking/lockdep.c:3827
Code: 00 0f 85 96 24 00 00 48 81 c4 f0 00 00 00 5b 41 5c 41 5d 41 5e 41 5f  
5d c3 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00 0f  
85 0b 28 00 00 49 81 3e 20 f9 df 8a 0f 84 5f ee ff
RSP: 0018:ffffc90007ac78d0 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000028 RSI: 0000000000000000 RDI: 0000000000000001
RBP: ffffc90007ac79e8 R08: 0000000000000001 R09: 0000000000000001
R10: fffffbfff1549320 R11: ffff8880375be640 R12: 0000000000000140
R13: 0000000000000000 R14: 0000000000000140 R15: 0000000000000000
FS:  00007f6dc39ee700(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2e625000 CR3: 00000000a8998000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600


---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

                 reply	other threads:[~2020-01-10 19:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=000000000000d9034c059bcddf3c@google.com \
    --to=syzbot+1edeee8da2474fe17a53@syzkaller.appspotmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    /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.