From: syzbot <syzbot+49f84b6782afe2a2b20e@syzkaller.appspotmail.com>
To: bp@alien8.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
luto@kernel.org, mingo@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: BUG: sleeping function called from invalid context in vdso_join_timens
Date: Wed, 02 Sep 2020 19:48:19 -0700 [thread overview]
Message-ID: <000000000000f0ae3005ae5fc85e@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 4d41ead6 Merge tag 'block-5.9-2020-08-28' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=174adf49900000
kernel config: https://syzkaller.appspot.com/x/.config?x=891ca5711a9f1650
dashboard link: https://syzkaller.appspot.com/bug?extid=49f84b6782afe2a2b20e
compiler: clang version 10.0.0 (https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
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+49f84b6782afe2a2b20e@syzkaller.appspotmail.com
BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:1491
in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 479, name: syz-executor.3
INFO: lockdep is turned off.
irq event stamp: 845
hardirqs last enabled at (845): [<ffffffff882cebdf>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160 [inline]
hardirqs last enabled at (845): [<ffffffff882cebdf>] _raw_spin_unlock_irqrestore+0x6f/0xd0 kernel/locking/spinlock.c:191
hardirqs last disabled at (844): [<ffffffff882cea28>] __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:108 [inline]
hardirqs last disabled at (844): [<ffffffff882cea28>] _raw_spin_lock_irqsave+0x78/0xc0 kernel/locking/spinlock.c:159
softirqs last enabled at (662): [<ffffffff88400f2f>] asm_call_on_stack+0xf/0x20 arch/x86/entry/entry_64.S:706
softirqs last disabled at (653): [<ffffffff88400f2f>] asm_call_on_stack+0xf/0x20 arch/x86/entry/entry_64.S:706
Preemption disabled at:
[<ffffffff882c3253>] preempt_schedule_irq+0x93/0x150 kernel/sched/core.c:4783
CPU: 1 PID: 479 Comm: syz-executor.3 Tainted: G D 5.9.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1f0/0x31e lib/dump_stack.c:118
___might_sleep+0x3c0/0x570 kernel/sched/core.c:7299
down_read+0x17/0x50 kernel/locking/rwsem.c:1491
mmap_read_lock include/linux/mmap_lock.h:46 [inline]
vdso_join_timens+0x46/0x120 arch/x86/entry/vdso/vma.c:147
kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
BUG: unable to handle page fault for address: ffff8880ae936310
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0011) - permissions violation
PGD c401067 P4D c401067 PUD 21ffff067 PMD 80000000ae8001e3
Oops: 0011 [#2] PREEMPT SMP KASAN
CPU: 1 PID: 479 Comm: syz-executor.3 Tainted: G D W 5.9.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
---
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:[~2020-09-03 2:48 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=000000000000f0ae3005ae5fc85e@google.com \
--to=syzbot+49f84b6782afe2a2b20e@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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