From: syzbot <syzbot+8e034d7422d389827720@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [ntfs3?] WARNING in attr_data_get_block (4)
Date: Mon, 08 Apr 2024 01:26:17 -0700 [thread overview]
Message-ID: <000000000000307a8e0615918f2b@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: fe46a7dd189e Merge tag 'sound-6.9-rc1' of git://git.kernel..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=10fbdda1180000
kernel config: https://syzkaller.appspot.com/x/.config?x=1a07d5da4eb21586
dashboard link: https://syzkaller.appspot.com/bug?extid=8e034d7422d389827720
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=171bf3a9180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1084f189180000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b42ab0fd4947/disk-fe46a7dd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b8a6e7231930/vmlinux-fe46a7dd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4fbf3e4ce6f8/bzImage-fe46a7dd.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/7a991be8b13a/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8e034d7422d389827720@syzkaller.appspotmail.com
R13: 00007ffd11b1eed8 R14: 431bde82d7b634db R15: 00007fad9422c03b
</TASK>
------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON(sem->magic != sem): count = 0x100, magic = 0x0, owner = 0xffff888022b61e01, curr 0xffff888022b61e00, list not empty
WARNING: CPU: 0 PID: 5077 at kernel/locking/rwsem.c:1342 __up_read+0x508/0x760 kernel/locking/rwsem.c:1342
Modules linked in:
CPU: 0 PID: 5077 Comm: syz-executor179 Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:__up_read+0x508/0x760 kernel/locking/rwsem.c:1342
Code: 24 10 80 3c 02 00 0f 85 21 02 00 00 48 8b 13 41 57 48 c7 c6 a0 bf 0c 8b 48 c7 c7 e0 bf 0c 8b 4c 8b 4c 24 08 e8 39 9a e5 ff 90 <0f> 0b 90 90 5f e9 c3 fe ff ff c6 05 2c 8a 1d 0e 01 90 4c 8d 7b 58
RSP: 0018:ffffc900043c6338 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff8880792208a0 RCX: ffffffff8150f3e9
RDX: ffff888022b61e00 RSI: ffffffff8150f3f6 RDI: 0000000000000001
RBP: ffffffff8f9f76b4 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: ffff8880792208a8
R13: 1ffff92000878c6b R14: ffff888079220908 R15: ffffffff8b0cbf60
FS: 00005555685f1380(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fad9427a100 CR3: 0000000078f48000 CR4: 0000000000350ef0
Call Trace:
<TASK>
attr_data_get_block+0x1f9/0x1b70 fs/ntfs3/attrib.c:905
ntfs_get_block_vbo+0x288/0xec0 fs/ntfs3/inode.c:587
do_mpage_readpage+0x663/0x17c0 fs/mpage.c:232
mpage_readahead+0x34d/0x590 fs/mpage.c:381
ntfs_readahead+0x1f7/0x250 fs/ntfs3/inode.c:755
read_pages+0x1ab/0xda0 mm/readahead.c:160
page_cache_ra_unbounded+0x455/0x5f0 mm/readahead.c:269
do_page_cache_ra mm/readahead.c:299 [inline]
page_cache_ra_order+0x7b7/0xa70 mm/readahead.c:544
ondemand_readahead+0x520/0x1140 mm/readahead.c:666
page_cache_sync_ra+0x174/0x1d0 mm/readahead.c:693
page_cache_sync_readahead include/linux/pagemap.h:1300 [inline]
filemap_get_pages+0xc0f/0x1840 mm/filemap.c:2507
filemap_read+0x39b/0xcf0 mm/filemap.c:2603
generic_file_read_iter+0x350/0x460 mm/filemap.c:2784
ntfs_file_read_iter+0x258/0x330 fs/ntfs3/file.c:768
__kernel_read+0x3ef/0xb20 fs/read_write.c:434
integrity_kernel_read+0x7f/0xb0 security/integrity/iint.c:28
ima_calc_file_hash_tfm+0x2cf/0x3e0 security/integrity/ima/ima_crypto.c:485
ima_calc_file_shash security/integrity/ima/ima_crypto.c:516 [inline]
ima_calc_file_hash+0x1c6/0x4a0 security/integrity/ima/ima_crypto.c:573
ima_collect_measurement+0x7eb/0x950 security/integrity/ima/ima_api.c:291
process_measurement+0x11ae/0x2100 security/integrity/ima/ima_main.c:359
ima_file_check+0xc1/0x110 security/integrity/ima/ima_main.c:559
security_file_post_open+0x70/0xc0 security/security.c:2975
do_open fs/namei.c:3644 [inline]
path_openat+0x17ad/0x2990 fs/namei.c:3799
do_file_open_root+0x2dd/0x5b0 fs/namei.c:3851
file_open_root+0x2a8/0x450 fs/open.c:1386
do_handle_open+0x3c9/0x5c0 fs/fhandle.c:235
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xd5/0x260 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x6d/0x75
RIP: 0033:0x7fad941e3b19
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 17 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:00007ffd11b1ec88 EFLAGS: 00000246 ORIG_RAX: 0000000000000130
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fad941e3b19
RDX: 0000000000000000 RSI: 0000000020000240 RDI: 0000000000000005
RBP: 00007fad942765f0 R08: 00005555685f24c0 R09: 00005555685f24c0
R10: 00005555685f24c0 R11: 0000000000000246 R12: 00007ffd11b1ecb0
R13: 00007ffd11b1eed8 R14: 431bde82d7b634db R15: 00007fad9422c03b
</TASK>
---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
reply other threads:[~2024-04-08 8:26 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=000000000000307a8e0615918f2b@google.com \
--to=syzbot+8e034d7422d389827720@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
/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.