From: John Fastabend <john.fastabend@gmail.com>
To: syzbot <syzbot+a861f52659ae2596492b@syzkaller.appspotmail.com>,
bpf@vger.kernel.org, ebiggers@kernel.org,
john.fastabend@gmail.com, linux-kernel@vger.kernel.org,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de
Subject: Re: WARNING in mark_lock
Date: Mon, 08 Jul 2019 09:21:17 -0700 [thread overview]
Message-ID: <5d236d7dc1db6_75f52af7c83505bcc3@john-XPS-13-9370.notmuch> (raw)
In-Reply-To: <0000000000007eb42d058c9836ac@google.com>
syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer still triggered
> crash:
> KASAN: use-after-free Read in class_equal
>
> ==================================================================
> BUG: KASAN: use-after-free in class_equal+0x40/0x50
> kernel/locking/lockdep.c:1527
> Read of size 8 at addr ffff88808a268ba0 by task syz-executor.1/9270
>
> CPU: 0 PID: 9270 Comm: syz-executor.1 Not tainted 5.2.0-rc3+ #1
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> Call Trace:
>
> Allocated by task 2647419968:
> BUG: unable to handle page fault for address: ffffffff8c00b020
> #PF: supervisor read access in kernel mode
> #PF: error_code(0x0000) - not-present page
> PGD 8a70067 P4D 8a70067 PUD 8a71063 PMD 0
> Thread overran stack, or stack corrupted
> Oops: 0000 [#1] PREEMPT SMP KASAN
> CPU: 0 PID: 9270 Comm: syz-executor.1 Not tainted 5.2.0-rc3+ #1
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> RIP: 0010:stack_depot_fetch+0x10/0x30 lib/stackdepot.c:203
> Code: e9 7b fd ff ff 4c 89 ff e8 8d b4 62 fe e9 e6 fd ff ff 90 90 90 90 90
> 90 90 90 89 f8 c1 ef 11 25 ff ff 1f 00 81 e7 f0 3f 00 00 <48> 03 3c c5 20
> 6c 04 8b 48 8d 47 18 48 89 06 8b 47 0c c3 0f 1f 00
> RSP: 0018:ffff88808a2688e8 EFLAGS: 00010006
> RAX: 00000000001f8880 RBX: ffff88808a269304 RCX: 0000000000000000
> RDX: 0000000000000000 RSI: ffff88808a2688f0 RDI: 0000000000003ff0
> RBP: ffff88808a268908 R08: 0000000000000020 R09: ffffed1015d044fa
> R10: ffffed1015d044f9 R11: ffff8880ae8227cf R12: ffffea0002289a00
> R13: ffff88808a268ba0 R14: ffff8880aa58ec40 R15: ffff88808a269300
> FS: 00005555570ba940(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: ffffffff8c00b020 CR3: 000000008dd00000 CR4: 00000000001406f0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
> Modules linked in:
> CR2: ffffffff8c00b020
> ---[ end trace 4acfe4b59fbc9cdb ]---
> RIP: 0010:stack_depot_fetch+0x10/0x30 lib/stackdepot.c:203
> Code: e9 7b fd ff ff 4c 89 ff e8 8d b4 62 fe e9 e6 fd ff ff 90 90 90 90 90
> 90 90 90 89 f8 c1 ef 11 25 ff ff 1f 00 81 e7 f0 3f 00 00 <48> 03 3c c5 20
> 6c 04 8b 48 8d 47 18 48 89 06 8b 47 0c c3 0f 1f 00
> RSP: 0018:ffff88808a2688e8 EFLAGS: 00010006
> RAX: 00000000001f8880 RBX: ffff88808a269304 RCX: 0000000000000000
> RDX: 0000000000000000 RSI: ffff88808a2688f0 RDI: 0000000000003ff0
> RBP: ffff88808a268908 R08: 0000000000000020 R09: ffffed1015d044fa
> R10: ffffed1015d044f9 R11: ffff8880ae8227cf R12: ffffea0002289a00
> R13: ffff88808a268ba0 R14: ffff8880aa58ec40 R15: ffff88808a269300
> FS: 00005555570ba940(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: ffffffff8c00b020 CR3: 000000008dd00000 CR4: 00000000001406f0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
>
>
> Tested on:
>
> commit: 0b58d013 bpf: tls, implement unhash to avoid transition ou..
> git tree: git://github.com/cilium/linux ktls-unhash
> console output: https://syzkaller.appspot.com/x/log.txt?x=153368a3a00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=2cc918d28ebd06b4
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
>
#syz test: git://github.com/cilium/linux fix-unhash
next prev parent reply other threads:[~2019-07-08 16:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 1:37 syzbot
2019-06-25 6:20 ` Thomas Gleixner
2019-06-25 7:29 ` [net/bpf] " Eric Biggers
2019-07-01 5:32 ` John Fastabend
2019-07-01 5:51 ` syzbot
2019-07-08 16:21 ` John Fastabend [this message]
2019-07-08 22:03 ` syzbot
2019-06-25 11:03 ` Peter Zijlstra
2019-06-25 11:06 ` Peter Zijlstra
2019-06-25 12:07 ` Dmitry Vyukov
2019-06-25 14:01 ` Peter Zijlstra
2019-06-25 14:10 ` Dmitry Vyukov
2019-06-27 22:03 ` syzbot
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=5d236d7dc1db6_75f52af7c83505bcc3@john-XPS-13-9370.notmuch \
--to=john.fastabend@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=ebiggers@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=syzbot+a861f52659ae2596492b@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®