From: syzbot <syzbot+6c67d4224af196c99976@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, boqun.feng@gmail.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
llvm@lists.linux.dev, longman@redhat.com, mingo@redhat.com,
nathan@kernel.org, ndesaulniers@google.com,
ntfs3@lists.linux.dev, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, trix@redhat.com,
will@kernel.org
Subject: Re: [syzbot] WARNING in match_held_lock
Date: Sun, 02 Oct 2022 20:53:31 -0700 [thread overview]
Message-ID: <000000000000776f5005ea1949d8@google.com> (raw)
In-Reply-To: <00000000000068e76205e2ec0e6b@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: a962b54e162c Merge tag 'i2c-for-6.0-rc8' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11833a82880000
kernel config: https://syzkaller.appspot.com/x/.config?x=755695d26ad09807
dashboard link: https://syzkaller.appspot.com/bug?extid=6c67d4224af196c99976
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13b51e14880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10b33c68880000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c0d6002d7b4b/disk-a962b54e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cf0a29408406/vmlinux-a962b54e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+6c67d4224af196c99976@syzkaller.appspotmail.com
ntfs3: loop3: Different NTFS' sector size (1024) and media sector size (512)
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(!hlock->nest_lock)
WARNING: CPU: 0 PID: 5565 at kernel/locking/lockdep.c:5135 match_held_lock+0xad/0xc0 kernel/locking/lockdep.c:5135
Modules linked in:
CPU: 0 PID: 5565 Comm: syz-executor151 Not tainted 6.0.0-rc7-syzkaller-00250-ga962b54e162c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
RIP: 0010:match_held_lock+0xad/0xc0 kernel/locking/lockdep.c:5135
Code: e8 b8 c4 7a fa 85 c0 74 e4 8b 05 26 e5 5e 04 85 c0 75 da 48 c7 c6 60 ac ec 89 48 c7 c7 e0 a8 ec 89 89 44 24 04 e8 45 e7 ba ff <0f> 0b 8b 44 24 04 eb bd 66 66 2e 0f 1f 84 00 00 00 00 00 41 57 41
RSP: 0018:ffffc900058c79d8 EFLAGS: 00010086
RAX: 0000000000000000 RBX: ffff88807e390aa0 RCX: 0000000000000000
RDX: ffff88807e390000 RSI: ffffffff8161f2a8 RDI: fffff52000b18f2d
RBP: ffffffff8bf89640 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000002 R11: 0000000000000001 R12: ffff88807e390000
R13: ffff88807e390a78 R14: 00000000ffffffff R15: ffff88807e390aa0
FS: 0000555556d9c300(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fbbd6497056 CR3: 0000000016c2f000 CR4: 0000000000350ef0
Call Trace:
<TASK>
__lock_is_held kernel/locking/lockdep.c:5407 [inline]
lock_is_held_type+0xa7/0x140 kernel/locking/lockdep.c:5709
lock_is_held include/linux/lockdep.h:283 [inline]
rcu_read_lock_sched_held+0x3a/0x70 kernel/rcu/update.c:125
trace_lock_release include/trace/events/lock.h:69 [inline]
lock_release+0x560/0x780 kernel/locking/lockdep.c:5677
__raw_spin_unlock include/linux/spinlock_api_smp.h:141 [inline]
_raw_spin_unlock+0x12/0x40 kernel/locking/spinlock.c:186
spin_unlock include/linux/spinlock.h:389 [inline]
inode_sb_list_del fs/inode.c:505 [inline]
evict+0x2aa/0x6b0 fs/inode.c:654
iput_final fs/inode.c:1748 [inline]
iput.part.0+0x55d/0x810 fs/inode.c:1774
iput+0x58/0x70 fs/inode.c:1764
ntfs_fill_super+0x2e89/0x37f0 fs/ntfs3/super.c:1190
get_tree_bdev+0x440/0x760 fs/super.c:1323
vfs_get_tree+0x89/0x2f0 fs/super.c:1530
do_new_mount fs/namespace.c:3040 [inline]
path_mount+0x1326/0x1e20 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fbbd6459e7a
Code: 48 c7 c2 c0 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 c8 03 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd6a35b568 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fbbd6459e7a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffd6a35b580
RBP: 00007ffd6a35b580 R08: 00007ffd6a35b5c0 R09: 00007ffd6a35b5c0
R10: 0000000000000000 R11: 0000000000000286 R12: 0000000000000004
R13: 00007ffd6a35b5c0 R14: 000000000000010e R15: 0000000020001b50
</TASK>
prev parent reply other threads:[~2022-10-03 3:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 19:59 [syzbot] WARNING in match_held_lock syzbot
2022-10-03 3:53 ` syzbot [this message]
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=000000000000776f5005ea1949d8@google.com \
--to=syzbot+6c67d4224af196c99976@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ntfs3@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.com \
--cc=will@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 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.