From: syzbot <syzbot+41a393c8d33874c463e9@syzkaller.appspotmail.com>
To: adobriyan@gmail.com, akpm@linux-foundation.org,
casey@schaufler-ca.com, christian@brauner.io, elver@google.com,
keescook@chromium.org, kent.overstreet@gmail.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mhocko@suse.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de
Subject: KCSAN: data-race in pid_update_inode / pid_update_inode
Date: Tue, 07 Jan 2020 00:17:09 -0800 [thread overview]
Message-ID: <000000000000004d9d059b88678a@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 245a4300 Merge branch 'rcu/kcsan' into tip/locking/kcsan
git tree: https://github.com/google/ktsan.git kcsan
console output: https://syzkaller.appspot.com/x/log.txt?x=123776e1e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a38292766f8efdaa
dashboard link: https://syzkaller.appspot.com/bug?extid=41a393c8d33874c463e9
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+41a393c8d33874c463e9@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in pid_update_inode / pid_update_inode
read to 0xffff88812b806828 of 2 bytes by task 11180 on cpu 1:
pid_update_inode+0x25/0x70 fs/proc/base.c:1818
pid_revalidate+0x91/0x120 fs/proc/base.c:1841
d_revalidate fs/namei.c:758 [inline]
d_revalidate fs/namei.c:755 [inline]
lookup_fast+0x612/0x6c0 fs/namei.c:1618
do_last fs/namei.c:3291 [inline]
path_openat+0x2ac/0x3580 fs/namei.c:3537
do_filp_open+0x11e/0x1b0 fs/namei.c:3567
do_sys_open+0x3b3/0x4f0 fs/open.c:1097
__do_sys_open fs/open.c:1115 [inline]
__se_sys_open fs/open.c:1110 [inline]
__x64_sys_open+0x55/0x70 fs/open.c:1110
do_syscall_64+0xcc/0x3a0 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x44/0xa9
write to 0xffff88812b806828 of 2 bytes by task 11178 on cpu 0:
pid_update_inode+0x51/0x70 fs/proc/base.c:1820
pid_revalidate+0x91/0x120 fs/proc/base.c:1841
d_revalidate fs/namei.c:758 [inline]
d_revalidate fs/namei.c:755 [inline]
lookup_fast+0x612/0x6c0 fs/namei.c:1618
do_last fs/namei.c:3291 [inline]
path_openat+0x2ac/0x3580 fs/namei.c:3537
do_filp_open+0x11e/0x1b0 fs/namei.c:3567
do_sys_open+0x3b3/0x4f0 fs/open.c:1097
__do_sys_open fs/open.c:1115 [inline]
__se_sys_open fs/open.c:1110 [inline]
__x64_sys_open+0x55/0x70 fs/open.c:1110
do_syscall_64+0xcc/0x3a0 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 11178 Comm: ps Not tainted 5.5.0-rc1-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
==================================================================
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
reply other threads:[~2020-01-07 8:17 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=000000000000004d9d059b88678a@google.com \
--to=syzbot+41a393c8d33874c463e9@syzkaller.appspotmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=casey@schaufler-ca.com \
--cc=christian@brauner.io \
--cc=elver@google.com \
--cc=keescook@chromium.org \
--cc=kent.overstreet@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).