* KCSAN: data-race in binder_dec_node_nilocked / binder_state_show
@ 2020-04-03 12:35 ` syzbot
0 siblings, 0 replies; 4+ messages in thread
From: syzbot @ 2020-04-03 12:35 UTC (permalink / raw)
To: arve, christian, devel, elver, gregkh, joel, linux-kernel, maco,
syzkaller-bugs, tkjos
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=106b67f1e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a4b9db179318d21f
dashboard link: https://syzkaller.appspot.com/bug?extid=71f39766a98dddab97b5
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+71f39766a98dddab97b5@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in binder_dec_node_nilocked / binder_state_show
write to 0xffff88809f276954 of 4 bytes by task 1408 on cpu 0:
binder_state_show+0xd8/0x260 drivers/android/binder.c:5938
seq_read+0x350/0x9d0 fs/seq_file.c:229
full_proxy_read+0xbd/0x100 fs/debugfs/file.c:220
do_loop_readv_writev fs/read_write.c:714 [inline]
do_loop_readv_writev fs/read_write.c:701 [inline]
do_iter_read+0x357/0x3d0 fs/read_write.c:935
vfs_readv+0x9c/0xf0 fs/read_write.c:997
do_preadv+0x131/0x1d0 fs/read_write.c:1089
__do_sys_preadv fs/read_write.c:1139 [inline]
__se_sys_preadv fs/read_write.c:1134 [inline]
__x64_sys_preadv+0x61/0x80 fs/read_write.c:1134
do_syscall_64+0xcc/0x3a0 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x44/0xa9
read to 0xffff88809f276954 of 4 bytes by task 1416 on cpu 1:
binder_dec_node_nilocked+0x382/0x610 drivers/android/binder.c:1261
binder_dec_node_tmpref+0xa3/0x120 drivers/android/binder.c:1379
binder_put_node drivers/android/binder.c:1387 [inline]
binder_state_show+0x1aa/0x260 drivers/android/binder.c:5950
seq_read+0x350/0x9d0 fs/seq_file.c:229
full_proxy_read+0xbd/0x100 fs/debugfs/file.c:220
do_loop_readv_writev fs/read_write.c:714 [inline]
do_loop_readv_writev fs/read_write.c:701 [inline]
do_iter_read+0x357/0x3d0 fs/read_write.c:935
vfs_readv+0x9c/0xf0 fs/read_write.c:997
do_preadv+0x131/0x1d0 fs/read_write.c:1089
__do_sys_preadv fs/read_write.c:1139 [inline]
__se_sys_preadv fs/read_write.c:1134 [inline]
__x64_sys_preadv+0x61/0x80 fs/read_write.c:1134
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: 1 PID: 1416 Comm: syz-executor.1 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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* KCSAN: data-race in binder_dec_node_nilocked / binder_state_show
@ 2020-04-03 12:35 ` syzbot
0 siblings, 0 replies; 4+ messages in thread
From: syzbot @ 2020-04-03 12:35 UTC (permalink / raw)
To: arve, christian, devel, elver, gregkh, joel, linux-kernel, maco,
syzkaller-bugs, tkjos
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=106b67f1e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a4b9db179318d21f
dashboard link: https://syzkaller.appspot.com/bug?extid=71f39766a98dddab97b5
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+71f39766a98dddab97b5@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in binder_dec_node_nilocked / binder_state_show
write to 0xffff88809f276954 of 4 bytes by task 1408 on cpu 0:
binder_state_show+0xd8/0x260 drivers/android/binder.c:5938
seq_read+0x350/0x9d0 fs/seq_file.c:229
full_proxy_read+0xbd/0x100 fs/debugfs/file.c:220
do_loop_readv_writev fs/read_write.c:714 [inline]
do_loop_readv_writev fs/read_write.c:701 [inline]
do_iter_read+0x357/0x3d0 fs/read_write.c:935
vfs_readv+0x9c/0xf0 fs/read_write.c:997
do_preadv+0x131/0x1d0 fs/read_write.c:1089
__do_sys_preadv fs/read_write.c:1139 [inline]
__se_sys_preadv fs/read_write.c:1134 [inline]
__x64_sys_preadv+0x61/0x80 fs/read_write.c:1134
do_syscall_64+0xcc/0x3a0 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x44/0xa9
read to 0xffff88809f276954 of 4 bytes by task 1416 on cpu 1:
binder_dec_node_nilocked+0x382/0x610 drivers/android/binder.c:1261
binder_dec_node_tmpref+0xa3/0x120 drivers/android/binder.c:1379
binder_put_node drivers/android/binder.c:1387 [inline]
binder_state_show+0x1aa/0x260 drivers/android/binder.c:5950
seq_read+0x350/0x9d0 fs/seq_file.c:229
full_proxy_read+0xbd/0x100 fs/debugfs/file.c:220
do_loop_readv_writev fs/read_write.c:714 [inline]
do_loop_readv_writev fs/read_write.c:701 [inline]
do_iter_read+0x357/0x3d0 fs/read_write.c:935
vfs_readv+0x9c/0xf0 fs/read_write.c:997
do_preadv+0x131/0x1d0 fs/read_write.c:1089
__do_sys_preadv fs/read_write.c:1139 [inline]
__se_sys_preadv fs/read_write.c:1134 [inline]
__x64_sys_preadv+0x61/0x80 fs/read_write.c:1134
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: 1 PID: 1416 Comm: syz-executor.1 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.
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: KCSAN: data-race in binder_dec_node_nilocked / binder_state_show
2020-04-03 12:35 ` syzbot
@ 2020-04-03 15:23 ` Todd Kjos
-1 siblings, 0 replies; 4+ messages in thread
From: Todd Kjos @ 2020-04-03 15:23 UTC (permalink / raw)
To: syzbot
Cc: Arve Hjønnevåg, Christian Brauner,
open list:ANDROID DRIVERS, elver, Greg Kroah-Hartman,
Joel Fernandes (Google),
LKML, Martijn Coenen, syzkaller-bugs, Todd Kjos
+Hridya Valsaraju
On Fri, Apr 3, 2020 at 5:35 AM syzbot
<syzbot+71f39766a98dddab97b5@syzkaller.appspotmail.com> wrote:
>
> 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=106b67f1e00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a4b9db179318d21f
> dashboard link: https://syzkaller.appspot.com/bug?extid=71f39766a98dddab97b5
> 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+71f39766a98dddab97b5@syzkaller.appspotmail.com
>
> ==================================================================
> BUG: KCSAN: data-race in binder_dec_node_nilocked / binder_state_show
>
> write to 0xffff88809f276954 of 4 bytes by task 1408 on cpu 0:
> binder_state_show+0xd8/0x260 drivers/android/binder.c:5938
> seq_read+0x350/0x9d0 fs/seq_file.c:229
> full_proxy_read+0xbd/0x100 fs/debugfs/file.c:220
> do_loop_readv_writev fs/read_write.c:714 [inline]
> do_loop_readv_writev fs/read_write.c:701 [inline]
> do_iter_read+0x357/0x3d0 fs/read_write.c:935
> vfs_readv+0x9c/0xf0 fs/read_write.c:997
> do_preadv+0x131/0x1d0 fs/read_write.c:1089
> __do_sys_preadv fs/read_write.c:1139 [inline]
> __se_sys_preadv fs/read_write.c:1134 [inline]
> __x64_sys_preadv+0x61/0x80 fs/read_write.c:1134
> do_syscall_64+0xcc/0x3a0 arch/x86/entry/common.c:294
> entry_SYSCALL_64_after_hwframe+0x44/0xa9
>
> read to 0xffff88809f276954 of 4 bytes by task 1416 on cpu 1:
> binder_dec_node_nilocked+0x382/0x610 drivers/android/binder.c:1261
> binder_dec_node_tmpref+0xa3/0x120 drivers/android/binder.c:1379
> binder_put_node drivers/android/binder.c:1387 [inline]
> binder_state_show+0x1aa/0x260 drivers/android/binder.c:5950
> seq_read+0x350/0x9d0 fs/seq_file.c:229
> full_proxy_read+0xbd/0x100 fs/debugfs/file.c:220
> do_loop_readv_writev fs/read_write.c:714 [inline]
> do_loop_readv_writev fs/read_write.c:701 [inline]
> do_iter_read+0x357/0x3d0 fs/read_write.c:935
> vfs_readv+0x9c/0xf0 fs/read_write.c:997
> do_preadv+0x131/0x1d0 fs/read_write.c:1089
> __do_sys_preadv fs/read_write.c:1139 [inline]
> __se_sys_preadv fs/read_write.c:1134 [inline]
> __x64_sys_preadv+0x61/0x80 fs/read_write.c:1134
> 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: 1 PID: 1416 Comm: syz-executor.1 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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: KCSAN: data-race in binder_dec_node_nilocked / binder_state_show
@ 2020-04-03 15:23 ` Todd Kjos
0 siblings, 0 replies; 4+ messages in thread
From: Todd Kjos @ 2020-04-03 15:23 UTC (permalink / raw)
To: syzbot
Cc: open list:ANDROID DRIVERS, elver, Todd Kjos, Greg Kroah-Hartman,
syzkaller-bugs, LKML, Arve Hjønnevåg,
Joel Fernandes (Google),
Martijn Coenen, Christian Brauner
+Hridya Valsaraju
On Fri, Apr 3, 2020 at 5:35 AM syzbot
<syzbot+71f39766a98dddab97b5@syzkaller.appspotmail.com> wrote:
>
> 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=106b67f1e00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a4b9db179318d21f
> dashboard link: https://syzkaller.appspot.com/bug?extid=71f39766a98dddab97b5
> 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+71f39766a98dddab97b5@syzkaller.appspotmail.com
>
> ==================================================================
> BUG: KCSAN: data-race in binder_dec_node_nilocked / binder_state_show
>
> write to 0xffff88809f276954 of 4 bytes by task 1408 on cpu 0:
> binder_state_show+0xd8/0x260 drivers/android/binder.c:5938
> seq_read+0x350/0x9d0 fs/seq_file.c:229
> full_proxy_read+0xbd/0x100 fs/debugfs/file.c:220
> do_loop_readv_writev fs/read_write.c:714 [inline]
> do_loop_readv_writev fs/read_write.c:701 [inline]
> do_iter_read+0x357/0x3d0 fs/read_write.c:935
> vfs_readv+0x9c/0xf0 fs/read_write.c:997
> do_preadv+0x131/0x1d0 fs/read_write.c:1089
> __do_sys_preadv fs/read_write.c:1139 [inline]
> __se_sys_preadv fs/read_write.c:1134 [inline]
> __x64_sys_preadv+0x61/0x80 fs/read_write.c:1134
> do_syscall_64+0xcc/0x3a0 arch/x86/entry/common.c:294
> entry_SYSCALL_64_after_hwframe+0x44/0xa9
>
> read to 0xffff88809f276954 of 4 bytes by task 1416 on cpu 1:
> binder_dec_node_nilocked+0x382/0x610 drivers/android/binder.c:1261
> binder_dec_node_tmpref+0xa3/0x120 drivers/android/binder.c:1379
> binder_put_node drivers/android/binder.c:1387 [inline]
> binder_state_show+0x1aa/0x260 drivers/android/binder.c:5950
> seq_read+0x350/0x9d0 fs/seq_file.c:229
> full_proxy_read+0xbd/0x100 fs/debugfs/file.c:220
> do_loop_readv_writev fs/read_write.c:714 [inline]
> do_loop_readv_writev fs/read_write.c:701 [inline]
> do_iter_read+0x357/0x3d0 fs/read_write.c:935
> vfs_readv+0x9c/0xf0 fs/read_write.c:997
> do_preadv+0x131/0x1d0 fs/read_write.c:1089
> __do_sys_preadv fs/read_write.c:1139 [inline]
> __se_sys_preadv fs/read_write.c:1134 [inline]
> __x64_sys_preadv+0x61/0x80 fs/read_write.c:1134
> 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: 1 PID: 1416 Comm: syz-executor.1 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.
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-04-03 15:23 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-03 12:35 KCSAN: data-race in binder_dec_node_nilocked / binder_state_show syzbot
2020-04-03 12:35 ` syzbot
2020-04-03 15:23 ` Todd Kjos
2020-04-03 15:23 ` Todd Kjos
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.