Groups
Sign in
Groups
syzkaller-android-bugs
Conversations
About
Send feedback
Help
WARNING in corrupted
5 views
Skip to first unread message
syzbot
unread,
Jun 14, 2019, 11:02:06 AM
6/14/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to syzkaller-a...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 4edd10cd BACKPORT: kheaders: Do not regenerate archive if ..
git tree: android-4.14
console output:
https://syzkaller.appspot.com/x/log.txt?x=123b53caa00000
kernel config:
https://syzkaller.appspot.com/x/.config?x=80e7cfd4aaae3023
dashboard link:
https://syzkaller.appspot.com/bug?extid=6411c37f02a74ed1012e
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=125dc549a00000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=147df3caa00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by:
syzbot+6411c3...@syzkaller.appspotmail.com
random: sshd: uninitialized urandom read (32 bytes read)
audit: type=1400 audit(1560520697.268:7): avc: denied { map } for
pid=1784 comm="syz-executor789" path="/root/syz-executor789171377"
dev="sda1" ino=16482 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023
tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1
------------[ cut here ]------------
WARNING: CPU: 0 PID: 2109 at fs/attr.c:213 notify_change2+0xab8/0xd70
fs/attr.c:213
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 2109 Comm: syz-executor789 Not tainted 4.14.125+ #6
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0xb9/0x10e lib/dump_stack.c:53
panic+0x1d9/0x3c2 kernel/panic.c:182
__warn.cold+0x2f/0x3b kernel/panic.c:546
Kernel Offset: 0x1d800000 from 0xffffffff81000000 (relocation range:
0xffffffff80000000-0xffffffffbfffffff)
Rebooting in 86400 seconds..
---
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
syzk...@googlegroups.com
.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status
for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages