* Re: BUG: using __this_cpu_read() in preemptible code in trace_hardirqs_on
[not found] <000000000000e921b305b18ba0a7@google.com>
@ 2020-10-16 17:16 ` syzbot
2020-10-16 20:33 ` syzbot
1 sibling, 0 replies; 3+ messages in thread
From: syzbot @ 2020-10-16 17:16 UTC (permalink / raw)
To: linux-kernel, mingo, netdev, peterz, rostedt, syzkaller-bugs
syzbot has found a reproducer for the following issue on:
HEAD commit: 9ff9b0d3 Merge tag 'net-next-5.10' of git://git.kernel.org..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16638607900000
kernel config: https://syzkaller.appspot.com/x/.config?x=d13c3fa80bc4bcc1
dashboard link: https://syzkaller.appspot.com/bug?extid=53f8ce8bbc07924b6417
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15b63310500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1565657f900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+53f8ce8bbc07924b6417@syzkaller.appspotmail.com
BUG: using __this_cpu_read() in preemptible [00000000] code: syz-executor089/6901
caller is lockdep_hardirqs_on_prepare+0x5e/0x450 kernel/locking/lockdep.c:4060
CPU: 0 PID: 6901 Comm: syz-executor089 Not tainted 5.9.0-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+0x198/0x1fb lib/dump_stack.c:118
check_preemption_disabled+0x128/0x130 lib/smp_processor_id.c:48
lockdep_hardirqs_on_prepare+0x5e/0x450 kernel/locking/lockdep.c:4060
trace_hardirqs_on+0x5b/0x1c0 kernel/trace/trace_preemptirq.c:49
__bad_area_nosemaphore+0xc6/0x4f0 arch/x86/mm/fault.c:797
do_user_addr_fault+0x852/0xbf0 arch/x86/mm/fault.c:1335
handle_page_fault arch/x86/mm/fault.c:1429 [inline]
exc_page_fault+0xa8/0x190 arch/x86/mm/fault.c:1482
asm_exc_page_fault+0x1e/0x30 arch/x86/include/asm/idtentry.h:583
RIP: 0033:0x4241f0
Code: 66 0f ef c0 66 0f ef c9 66 0f ef d2 66 0f ef db 48 89 f8 48 89 f9 48 81 e1 ff 0f 00 00 48 81 f9 cf 0f 00 00 77 74 48 83 e0 f0 <66> 0f 74 00 66 0f 74 48 10 66 0f 74 50 20 66 0f 74 58 30 66 0f d7
RSP: 002b:00007ffcacd310b8 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 00007ffcacd310e0 RCX: 0000000000000000
RDX: 0000000000000010 RSI: 000000000000000f RDI: 0000000000000000
RBP: 0000000000000003 R08: 00000000ffffffff R09: 0000000000000000
R10: 0000000000000000 R11: 000000000000000f R12: 0000000000401d70
R13: 0000000000401e00 R14: 0000000000000000 R15: 0000000000000000
BUG: using __this_cpu_read() in preemptible [00000000] code: syz-executor089/6901
caller is lockdep_hardirqs_on+0x34/0x110 kernel/locking/lockdep.c:4129
CPU: 0 PID: 6901 Comm: syz-executor089 Not tainted 5.9.0-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+0x198/0x1fb lib/dump_stack.c:118
check_preemption_disabled+0x128/0x130 lib/smp_processor_id.c:48
lockdep_hardirqs_on+0x34/0x110 kernel/locking/lockdep.c:4129
__bad_area_nosemaphore+0xc6/0x4f0 arch/x86/mm/fault.c:797
do_user_addr_fault+0x852/0xbf0 arch/x86/mm/fault.c:1335
handle_page_fault arch/x86/mm/fault.c:1429 [inline]
exc_page_fault+0xa8/0x190 arch/x86/mm/fault.c:1482
asm_exc_page_fault+0x1e/0x30 arch/x86/include/asm/idtentry.h:583
RIP: 0033:0x4241f0
Code: 66 0f ef c0 66 0f ef c9 66 0f ef d2 66 0f ef db 48 89 f8 48 89 f9 48 81 e1 ff 0f 00 00 48 81 f9 cf 0f 00 00 77 74 48 83 e0 f0 <66> 0f 74 00 66 0f 74 48 10 66 0f 74 50 20 66 0f 74 58 30 66 0f d7
RSP: 002b:00007ffcacd310b8 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 00007ffcacd310e0 RCX: 0000000000000000
RDX: 0000000000000010 RSI: 000000000000000f RDI: 0000000000000000
RBP: 0000000000000003 R08: 00000000ffffffff R09: 0000000000000000
R10: 0000000000000000 R11: 00000000000
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: BUG: using __this_cpu_read() in preemptible code in trace_hardirqs_on
[not found] <000000000000e921b305b18ba0a7@google.com>
2020-10-16 17:16 ` BUG: using __this_cpu_read() in preemptible code in trace_hardirqs_on syzbot
@ 2020-10-16 20:33 ` syzbot
2020-10-21 13:09 ` Dmitry Vyukov
1 sibling, 1 reply; 3+ messages in thread
From: syzbot @ 2020-10-16 20:33 UTC (permalink / raw)
To: linux-kernel, mingo, mingo, netdev, peterz, rostedt,
syzkaller-bugs, will
syzbot has bisected this issue to:
commit 4d004099a668c41522242aa146a38cc4eb59cb1e
Author: Peter Zijlstra <peterz@infradead.org>
Date: Fri Oct 2 09:04:21 2020 +0000
lockdep: Fix lockdep recursion
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=174a766f900000
start commit: 9ff9b0d3 Merge tag 'net-next-5.10' of git://git.kernel.org..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=14ca766f900000
console output: https://syzkaller.appspot.com/x/log.txt?x=10ca766f900000
kernel config: https://syzkaller.appspot.com/x/.config?x=d13c3fa80bc4bcc1
dashboard link: https://syzkaller.appspot.com/bug?extid=53f8ce8bbc07924b6417
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15b63310500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1565657f900000
Reported-by: syzbot+53f8ce8bbc07924b6417@syzkaller.appspotmail.com
Fixes: 4d004099a668 ("lockdep: Fix lockdep recursion")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: BUG: using __this_cpu_read() in preemptible code in trace_hardirqs_on
2020-10-16 20:33 ` syzbot
@ 2020-10-21 13:09 ` Dmitry Vyukov
0 siblings, 0 replies; 3+ messages in thread
From: Dmitry Vyukov @ 2020-10-21 13:09 UTC (permalink / raw)
To: syzbot
Cc: LKML, Ingo Molnar, Ingo Molnar, netdev, Peter Zijlstra,
Steven Rostedt, syzkaller-bugs, Will Deacon
On Fri, Oct 16, 2020 at 10:33 PM syzbot
<syzbot+53f8ce8bbc07924b6417@syzkaller.appspotmail.com> wrote:
>
> syzbot has bisected this issue to:
>
> commit 4d004099a668c41522242aa146a38cc4eb59cb1e
> Author: Peter Zijlstra <peterz@infradead.org>
> Date: Fri Oct 2 09:04:21 2020 +0000
>
> lockdep: Fix lockdep recursion
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=174a766f900000
> start commit: 9ff9b0d3 Merge tag 'net-next-5.10' of git://git.kernel.org..
> git tree: net-next
> final oops: https://syzkaller.appspot.com/x/report.txt?x=14ca766f900000
> console output: https://syzkaller.appspot.com/x/log.txt?x=10ca766f900000
> kernel config: https://syzkaller.appspot.com/x/.config?x=d13c3fa80bc4bcc1
> dashboard link: https://syzkaller.appspot.com/bug?extid=53f8ce8bbc07924b6417
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15b63310500000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1565657f900000
>
> Reported-by: syzbot+53f8ce8bbc07924b6417@syzkaller.appspotmail.com
> Fixes: 4d004099a668 ("lockdep: Fix lockdep recursion")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
This is now one of top crashers with 190K crashes in the past 12 days:
https://syzkaller.appspot.com/bug?id=e7cbd9d7047a1c4e14bbdc194a7d87de1f168289
This is now almost the only bug syzbot triggers.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-10-21 13:10 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <000000000000e921b305b18ba0a7@google.com>
2020-10-16 17:16 ` BUG: using __this_cpu_read() in preemptible code in trace_hardirqs_on syzbot
2020-10-16 20:33 ` syzbot
2020-10-21 13:09 ` Dmitry Vyukov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).