* Re: [syzbot] [vfs?] [ntfs3?] WARNING in path_openat
[not found] <000000000000a0d7f305eecfcbb9@google.com>
@ 2023-01-11 7:15 ` syzbot
2023-01-26 23:55 ` syzbot
2023-07-27 5:33 ` [syzbot] " syzbot
2 siblings, 0 replies; 4+ messages in thread
From: syzbot @ 2023-01-11 7:15 UTC (permalink / raw)
To: almaz.alexandrovich, linux-fsdevel, linux-kernel, ntfs3,
syzkaller-bugs, viro
syzbot has found a reproducer for the following issue on:
HEAD commit: 40c18f363a08 Merge tag '6.2-rc3-ksmbd-server-fixes' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14a30e1c480000
kernel config: https://syzkaller.appspot.com/x/.config?x=ebc110f9741920ed
dashboard link: https://syzkaller.appspot.com/bug?extid=be8872fcb764bf9fea73
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1505b0ce480000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4b974f49dd49/disk-40c18f36.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8d735ca0c438/vmlinux-40c18f36.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6aeef3d597b4/bzImage-40c18f36.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/e9ddd28ad880/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+be8872fcb764bf9fea73@syzkaller.appspotmail.com
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff88806a1ef1d0, owner = 0x0, curr 0xffff88802561ba80, list empty
WARNING: CPU: 1 PID: 10307 at kernel/locking/rwsem.c:1361 __up_write kernel/locking/rwsem.c:1360 [inline]
WARNING: CPU: 1 PID: 10307 at kernel/locking/rwsem.c:1361 up_write+0x4f9/0x580 kernel/locking/rwsem.c:1615
Modules linked in:
CPU: 1 PID: 10307 Comm: syz-executor.5 Not tainted 6.2.0-rc3-syzkaller-00014-g40c18f363a08 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:__up_write kernel/locking/rwsem.c:1360 [inline]
RIP: 0010:up_write+0x4f9/0x580 kernel/locking/rwsem.c:1615
Code: c7 00 ad ed 8a 48 c7 c6 a0 af ed 8a 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 31 c0 53 e8 9b 59 e8 ff 48 83 c4 08 <0f> 0b e9 6b fd ff ff 48 c7 c1 98 a4 96 8e 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc900053ef840 EFLAGS: 00010292
RAX: 7a73507bb1e00700 RBX: ffffffff8aedade0 RCX: ffff88802561ba80
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900053ef910 R08: ffffffff816f2c9d R09: fffff52000a7dec1
R10: fffff52000a7dec1 R11: 1ffff92000a7dec0 R12: 0000000000000000
R13: ffff88806a1ef1d0 R14: 1ffff92000a7df10 R15: dffffc0000000000
FS: 00007fd23b092700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555555ea4848 CR3: 000000001d10d000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:761 [inline]
open_last_lookups fs/namei.c:3485 [inline]
path_openat+0x14ff/0x2dd0 fs/namei.c:3711
do_filp_open+0x264/0x4f0 fs/namei.c:3741
do_sys_openat2+0x124/0x4e0 fs/open.c:1310
do_sys_open fs/open.c:1326 [inline]
__do_sys_openat fs/open.c:1342 [inline]
__se_sys_openat fs/open.c:1337 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1337
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fd23a28c0c9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 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 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fd23b092168 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fd23a3ac050 RCX: 00007fd23a28c0c9
RDX: 0000000000000240 RSI: 0000000020000000 RDI: ffffffffffffff9c
RBP: 00007fd23a2e7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffdfbd42a1f R14: 00007fd23b092300 R15: 0000000000022000
</TASK>
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [syzbot] [vfs?] [ntfs3?] WARNING in path_openat
[not found] <000000000000a0d7f305eecfcbb9@google.com>
2023-01-11 7:15 ` [syzbot] [vfs?] [ntfs3?] WARNING in path_openat syzbot
@ 2023-01-26 23:55 ` syzbot
2023-07-27 5:33 ` [syzbot] " syzbot
2 siblings, 0 replies; 4+ messages in thread
From: syzbot @ 2023-01-26 23:55 UTC (permalink / raw)
To: almaz.alexandrovich, linux-fsdevel, linux-kernel, ntfs3,
syzkaller-bugs, viro
syzbot has found a reproducer for the following issue on:
HEAD commit: 7c46948a6e9c Merge tag 'fs.fuse.acl.v6.2-rc6' of git://git..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=109c0b8e480000
kernel config: https://syzkaller.appspot.com/x/.config?x=c8d5c2ee6c2bd4b8
dashboard link: https://syzkaller.appspot.com/bug?extid=be8872fcb764bf9fea73
compiler: Debian clang version 13.0.1-6~deb11u1, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17346ee1480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=149c16cd480000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cc51645b6401/disk-7c46948a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/be036b5604a3/vmlinux-7c46948a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/274f5abf2c8f/bzImage-7c46948a.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/afb5c6b7a19b/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+be8872fcb764bf9fea73@syzkaller.appspotmail.com
------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff88807104ea70, owner = 0x0, curr 0xffff8880196757c0, list empty
WARNING: CPU: 0 PID: 7935 at kernel/locking/rwsem.c:1361 __up_write kernel/locking/rwsem.c:1360 [inline]
WARNING: CPU: 0 PID: 7935 at kernel/locking/rwsem.c:1361 up_write+0x4f9/0x580 kernel/locking/rwsem.c:1615
Modules linked in:
CPU: 0 PID: 7935 Comm: syz-executor316 Not tainted 6.2.0-rc5-syzkaller-00047-g7c46948a6e9c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
RIP: 0010:__up_write kernel/locking/rwsem.c:1360 [inline]
RIP: 0010:up_write+0x4f9/0x580 kernel/locking/rwsem.c:1615
Code: c7 00 ad ed 8a 48 c7 c6 a0 af ed 8a 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 31 c0 53 e8 9b 5a e8 ff 48 83 c4 08 <0f> 0b e9 6b fd ff ff 48 c7 c1 18 cb 96 8e 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc9000b7cf860 EFLAGS: 00010296
RAX: 4643b7f86e564100 RBX: ffffffff8aedade0 RCX: ffff8880196757c0
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc9000b7cf930 R08: ffffffff816f2b8d R09: fffff520016f9ec5
R10: fffff520016f9ec5 R11: 1ffff920016f9ec4 R12: 0000000000000000
R13: ffff88807104ea70 R14: 1ffff920016f9f14 R15: dffffc0000000000
FS: 00007ff043008700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000561cee05f058 CR3: 0000000021d9a000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:761 [inline]
open_last_lookups fs/namei.c:3485 [inline]
path_openat+0x14ff/0x2dd0 fs/namei.c:3711
do_filp_open+0x264/0x4f0 fs/namei.c:3741
do_sys_openat2+0x124/0x4e0 fs/open.c:1310
do_sys_open fs/open.c:1326 [inline]
__do_sys_creat fs/open.c:1402 [inline]
__se_sys_creat fs/open.c:1396 [inline]
__x64_sys_creat+0x11f/0x160 fs/open.c:1396
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7ff04b2814a9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 d1 15 00 00 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 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ff0430082f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007ff04b326790 RCX: 00007ff04b2814a9
RDX: 00007ff04b2814a9 RSI: 0000000000000106 RDI: 0000000020000200
RBP: 00007ff04b2f2c88 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000020000600
R13: 0030656c69662f2e R14: 0000000020000b80 R15: 00007ff04b326798
</TASK>
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [syzbot] [ntfs3?] WARNING in path_openat
[not found] <000000000000a0d7f305eecfcbb9@google.com>
2023-01-11 7:15 ` [syzbot] [vfs?] [ntfs3?] WARNING in path_openat syzbot
2023-01-26 23:55 ` syzbot
@ 2023-07-27 5:33 ` syzbot
2023-07-27 6:47 ` Aleksandr Nogikh
2 siblings, 1 reply; 4+ messages in thread
From: syzbot @ 2023-07-27 5:33 UTC (permalink / raw)
To: almaz.alexandrovich, bp, linux-fsdevel, linux-kernel, ntfs3,
syzkaller-bugs, viro, yazen.ghannam
syzbot suspects this issue was fixed by commit:
commit 00e4feb8c0476bbde3c8bf4a593e0f82ca9a4df6
Author: Yazen Ghannam <yazen.ghannam@amd.com>
Date: Fri Jan 27 17:04:03 2023 +0000
EDAC/amd64: Rename debug_display_dimm_sizes()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=157a6f81a80000
start commit: c1649ec55708 Merge tag 'nfsd-6.2-4' of git://git.kernel.or..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=319a3509d25b0f85
dashboard link: https://syzkaller.appspot.com/bug?extid=be8872fcb764bf9fea73
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17c604fe480000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: EDAC/amd64: Rename debug_display_dimm_sizes()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [syzbot] [ntfs3?] WARNING in path_openat
2023-07-27 5:33 ` [syzbot] " syzbot
@ 2023-07-27 6:47 ` Aleksandr Nogikh
0 siblings, 0 replies; 4+ messages in thread
From: Aleksandr Nogikh @ 2023-07-27 6:47 UTC (permalink / raw)
To: syzbot
Cc: almaz.alexandrovich, bp, linux-fsdevel, linux-kernel, ntfs3,
syzkaller-bugs, viro, yazen.ghannam
Please ignore this bisection result.
On Thu, Jul 27, 2023 at 7:33 AM syzbot
<syzbot+be8872fcb764bf9fea73@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit 00e4feb8c0476bbde3c8bf4a593e0f82ca9a4df6
> Author: Yazen Ghannam <yazen.ghannam@amd.com>
> Date: Fri Jan 27 17:04:03 2023 +0000
>
> EDAC/amd64: Rename debug_display_dimm_sizes()
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=157a6f81a80000
accumulated error probability: 0.50
< .. >
reproducer is flaky (0.11 repro chance estimate)
The reproducer was too unstable and the threshold for non-reporting is
currently exactly 0.5 :)
I'll decrease it.
> start commit: c1649ec55708 Merge tag 'nfsd-6.2-4' of git://git.kernel.or..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=319a3509d25b0f85
> dashboard link: https://syzkaller.appspot.com/bug?extid=be8872fcb764bf9fea73
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17c604fe480000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: EDAC/amd64: Rename debug_display_dimm_sizes()
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>
^ permalink raw reply [flat|nested] 4+ messages in thread