[Android 6.1] BUG: scheduling while atomic in kauditd_thread

0 views
Skip to first unread message

syzbot

unread,
Apr 20, 2024, 9:28:23 PMApr 20
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: dcb09569bbff ANDROID: ABI: Update symbol list for Exynos SoC
git tree: android14-6.1
console output: https://syzkaller.appspot.com/x/log.txt?x=15135e73180000
kernel config: https://syzkaller.appspot.com/x/.config?x=7bd1a415c6de5d9d
dashboard link: https://syzkaller.appspot.com/bug?extid=f989b9aa1412d65984db
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11a7f5f7180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16f946e3180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1c859de5ccc3/disk-dcb09569.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4d203a1271c9/vmlinux-dcb09569.xz
kernel image: https://storage.googleapis.com/syzbot-assets/81c9e4b783ab/bzImage-dcb09569.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f989b9...@syzkaller.appspotmail.com

audit: type=1400 audit(1713662690.267:69): avc: denied { perfmon } for pid=294 comm="syz-executor134" capability=38 scontext=root:sysadm_r:sysadm_t tcontext=root:sysadm_r:sysadm_t tclass=capability2 permissive=1
audit: type=1400 audit(1713662690.267:70): avc: denied { map_read map_write } for pid=294 comm="syz-executor134" scontext=root:sysadm_r:sysadm_t tcontext=root:sysadm_r:sysadm_t tclass=bpf permissive=1
audit: type=1400 audit(1713662690.267:71): avc: denied { prog_load } for pid=294 comm="syz-executor134" scontext=root:sysadm_r:sysadm_t tcontext=root:sysadm_r:sysadm_t tclass=bpf permissive=1
audit: type=1400 audit(1713662690.267:72): avc: denied { prog_run } for pid=294 comm="syz-executor134" scontext=root:sysadm_r:sysadm_t tcontext=root:sysadm_r:sysadm_t tclass=bpf permissive=1
BUG: scheduling while atomic: kauditd/28/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff815ae511>] __wake_up_klogd+0x21/0x110 kernel/printk/printk.c:3487
CPU: 1 PID: 28 Comm: kauditd Not tainted 6.1.75-syzkaller-00037-gdcb09569bbff #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
dump_stack+0x15/0x1b lib/dump_stack.c:113
__schedule_bug+0x195/0x260 kernel/sched/core.c:5960
schedule_debug kernel/sched/core.c:5987 [inline]
__schedule+0xcf7/0x1550 kernel/sched/core.c:6622
schedule+0xc3/0x180 kernel/sched/core.c:6805
kauditd_thread+0x630/0x740 kernel/audit.c:901
kthread+0x26d/0x300 kernel/kthread.c:386
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>


---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages