From: syzbot <syzbot+0d4522639ba75b02bf19@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com
Subject: KCSAN: data-race in __xa_clear_mark / xas_find_marked
Date: Mon, 10 Aug 2020 05:41:18 -0700 [thread overview]
Message-ID: <00000000000062a49205ac854581@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: fc80c51f Merge tag 'kbuild-v5.9' of git://git.kernel.org/p..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13cb73fa900000
kernel config: https://syzkaller.appspot.com/x/.config?x=997a92ee4b5588ef
dashboard link: https://syzkaller.appspot.com/bug?extid=0d4522639ba75b02bf19
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project.git ca2dcbd030eadbf0aa9b660efe864ff08af6e18b)
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0d4522639ba75b02bf19@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in __xa_clear_mark / xas_find_marked
write to 0xffff8880bace9b30 of 8 bytes by interrupt on cpu 1:
instrument_write include/linux/instrumented.h:42 [inline]
__test_and_clear_bit include/asm-generic/bitops/instrumented-non-atomic.h:85 [inline]
node_clear_mark lib/xarray.c:100 [inline]
xas_clear_mark lib/xarray.c:908 [inline]
__xa_clear_mark+0x229/0x350 lib/xarray.c:1726
test_clear_page_writeback+0x28d/0x480 mm/page-writeback.c:2739
end_page_writeback+0xa7/0x110 mm/filemap.c:1369
page_endio+0x1aa/0x1e0 mm/filemap.c:1400
mpage_end_io+0x186/0x1d0 fs/mpage.c:54
bio_endio+0x28a/0x370 block/bio.c:1447
req_bio_endio block/blk-core.c:259 [inline]
blk_update_request+0x535/0xbd0 block/blk-core.c:1576
blk_mq_end_request+0x22/0x50 block/blk-mq.c:562
lo_complete_rq+0xca/0x180 drivers/block/loop.c:500
blk_done_softirq+0x1a5/0x200 block/blk-mq.c:586
__do_softirq+0x198/0x360 kernel/softirq.c:298
run_ksoftirqd+0x2f/0x60 kernel/softirq.c:652
smpboot_thread_fn+0x347/0x530 kernel/smpboot.c:165
kthread+0x20d/0x230 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
read to 0xffff8880bace9b30 of 8 bytes by task 12715 on cpu 0:
xas_find_chunk include/linux/xarray.h:1625 [inline]
xas_find_marked+0x22f/0x6b0 lib/xarray.c:1198
find_get_pages_range_tag+0xa3/0x580 mm/filemap.c:1976
pagevec_lookup_range_tag+0x37/0x50 mm/swap.c:1120
__filemap_fdatawait_range+0xab/0x1b0 mm/filemap.c:519
filemap_fdatawait_range mm/filemap.c:554 [inline]
filemap_write_and_wait_range+0x119/0x2a0 mm/filemap.c:664
generic_file_read_iter+0x11d/0x3e0 mm/filemap.c:2375
call_read_iter include/linux/fs.h:1866 [inline]
generic_file_splice_read+0x22b/0x310 fs/splice.c:312
do_splice_to fs/splice.c:870 [inline]
splice_direct_to_actor+0x2a8/0x660 fs/splice.c:950
do_splice_direct+0xf2/0x170 fs/splice.c:1059
do_sendfile+0x56a/0xba0 fs/read_write.c:1540
__do_sys_sendfile64 fs/read_write.c:1595 [inline]
__se_sys_sendfile64 fs/read_write.c:1587 [inline]
__x64_sys_sendfile64+0xa9/0x130 fs/read_write.c:1587
do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 12715 Comm: syz-executor.4 Not tainted 5.8.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================
---
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.
next reply other threads:[~2020-08-10 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 12:41 syzbot [this message]
2020-08-10 12:45 ` KCSAN: data-race in __xa_clear_mark / xas_find_marked Matthew Wilcox
2020-08-10 12:59 ` Marco Elver
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=00000000000062a49205ac854581@google.com \
--to=syzbot+0d4522639ba75b02bf19@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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.