mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+88a9b535e28311efdcd4@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	tytso@mit.edu
Subject: [syzbot] KCSAN: data-race in copy_page_to_iter / strncpy (4)
Date: Thu, 10 Feb 2022 02:50:17 -0800	[thread overview]
Message-ID: <0000000000003e009a05d7a7b77f@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    e6251ab4551f Merge tag 'nfs-for-5.17-2' of git://git.linux..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=109133b4700000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1dcc3374da7c1f7c
dashboard link: https://syzkaller.appspot.com/bug?extid=88a9b535e28311efdcd4
compiler:       Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2

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+88a9b535e28311efdcd4@syzkaller.appspotmail.com

==================================================================
BUG: KCSAN: data-race in copy_page_to_iter / strncpy

write to 0xffff888108b1b488 of 1 bytes by task 16090 on cpu 1:
 strncpy+0xcf/0x150 lib/string.c:114
 ext4_sample_last_mounted fs/ext4/file.c:828 [inline]
 ext4_file_open+0x3a6/0x4e0 fs/ext4/file.c:847
 do_dentry_open+0x52c/0x860 fs/open.c:824
 vfs_open+0x43/0x50 fs/open.c:959
 do_open fs/namei.c:3476 [inline]
 path_openat+0x170c/0x1f30 fs/namei.c:3609
 do_filp_open+0x105/0x220 fs/namei.c:3636
 do_sys_openat2+0xb5/0x2b0 fs/open.c:1214
 do_sys_open fs/open.c:1230 [inline]
 __do_sys_open fs/open.c:1238 [inline]
 __se_sys_open fs/open.c:1234 [inline]
 __x64_sys_open+0xe2/0x110 fs/open.c:1234
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff888108b1b400 of 1024 bytes by task 10450 on cpu 0:
 instrument_copy_to_user include/linux/instrumented.h:119 [inline]
 copyout lib/iov_iter.c:154 [inline]
 copy_page_to_iter_iovec lib/iov_iter.c:226 [inline]
 __copy_page_to_iter lib/iov_iter.c:850 [inline]
 copy_page_to_iter+0x2cb/0x950 lib/iov_iter.c:878
 copy_folio_to_iter include/linux/uio.h:153 [inline]
 filemap_read+0x1126/0x1430 mm/filemap.c:2727
 blkdev_read_iter+0x2cc/0x380 block/fops.c:614
 call_read_iter include/linux/fs.h:2068 [inline]
 new_sync_read fs/read_write.c:400 [inline]
 vfs_read+0x66c/0x750 fs/read_write.c:481
 ksys_read+0xd9/0x190 fs/read_write.c:619
 __do_sys_read fs/read_write.c:629 [inline]
 __se_sys_read fs/read_write.c:627 [inline]
 __x64_sys_read+0x3e/0x50 fs/read_write.c:627
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 10450 Comm: udevd Not tainted 5.17.0-rc3-syzkaller-00029-ge6251ab4551f-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================
I/O error, dev loop2, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0


---
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.

                 reply	other threads:[~2022-02-10 10:50 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=0000000000003e009a05d7a7b77f@google.com \
    --to=syzbot+88a9b535e28311efdcd4@syzkaller.appspotmail.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tytso@mit.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®