From: Dmitry Vyukov <dvyukov@google.com> To: syzbot <syzbot+f09a12b2c77bfbbf51bd@syzkaller.appspotmail.com>, Mark Rutland <mark.rutland@arm.com>, Russell King - ARM Linux <linux@armlinux.org.uk>, Arnd Bergmann <arnd@arndb.de>, Linux ARM <linux-arm-kernel@lists.infradead.org> Cc: Alexandre Chartre <alexandre.chartre@oracle.com>, LKML <linux-kernel@vger.kernel.org>, Masami Hiramatsu <mhiramat@kernel.org>, Peter Zijlstra <peterz@infradead.org>, syzkaller-bugs <syzkaller-bugs@googlegroups.com>, Thomas Gleixner <tglx@linutronix.de> Subject: Re: [syzbot] upstream boot error: WARNING in __context_tracking_enter Date: Fri, 19 Mar 2021 10:54:48 +0100 [thread overview] Message-ID: <CACT4Y+bLkFSc8manYrCukj-_nzwVsV9y6xYWXmGyYFS-PoBRPQ@mail.gmail.com> (raw) In-Reply-To: <0000000000004f14c105bde08f75@google.com> .On Fri, Mar 19, 2021 at 10:44 AM syzbot <syzbot+f09a12b2c77bfbbf51bd@syzkaller.appspotmail.com> wrote: > > Hello, > > syzbot found the following issue on: > > HEAD commit: 8b12a62a Merge tag 'drm-fixes-2021-03-19' of git://anongit.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=17e815aed00000 > kernel config: https://syzkaller.appspot.com/x/.config?x=cfeed364fc353c32 > dashboard link: https://syzkaller.appspot.com/bug?extid=f09a12b2c77bfbbf51bd > userspace arch: arm > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+f09a12b2c77bfbbf51bd@syzkaller.appspotmail.com +Mark, arm It did not get far with CONFIG_CONTEXT_TRACKING_FORCE (kernel doesn't boot). > Run /sbin/init as init process > ------------[ cut here ]------------ > WARNING: CPU: 0 PID: 1 at include/linux/seqlock.h:271 __seqprop_assert include/linux/seqlock.h:271 [inline] > WARNING: CPU: 0 PID: 1 at include/linux/seqlock.h:271 __seqprop_assert.constprop.0+0xf0/0x11c include/linux/seqlock.h:269 > Modules linked in: > Kernel panic - not syncing: panic_on_warn set ... > CPU: 0 PID: 1 Comm: init Not tainted 5.12.0-rc3-syzkaller #0 > Hardware name: ARM-Versatile Express > Backtrace: > [<81804310>] (dump_backtrace) from [<81804584>] (show_stack+0x18/0x1c arch/arm/kernel/traps.c:252) > r7:00000080 r6:60000193 r5:00000000 r4:82b58444 > [<8180456c>] (show_stack) from [<8180bc58>] (__dump_stack lib/dump_stack.c:79 [inline]) > [<8180456c>] (show_stack) from [<8180bc58>] (dump_stack+0xb8/0xe8 lib/dump_stack.c:120) > [<8180bba0>] (dump_stack) from [<81805118>] (panic+0x130/0x378 kernel/panic.c:231) > r7:81f487d4 r6:82a390e4 r5:00000000 r4:82c6b0d8 > [<81804fe8>] (panic) from [<802447b4>] (__warn+0xb0/0x164 kernel/panic.c:605) > r3:82a2248c r2:00000000 r1:5b71e000 r0:81f487d4 > r7:0000010f > [<80244704>] (__warn) from [<818053c8>] (warn_slowpath_fmt+0x68/0xd4 kernel/panic.c:628) > r7:8028c4b4 r6:0000010f r5:81f40c30 r4:00000000 > [<81805364>] (warn_slowpath_fmt) from [<8028c4b4>] (__seqprop_assert include/linux/seqlock.h:271 [inline]) > [<81805364>] (warn_slowpath_fmt) from [<8028c4b4>] (__seqprop_assert.constprop.0+0xf0/0x11c include/linux/seqlock.h:269) > r8:00000000 r7:82a22498 r6:828ac940 r5:8181fbb0 r4:00000001 > [<8028c3c4>] (__seqprop_assert.constprop.0) from [<8028ea54>] (vtime_user_enter+0x1c/0x90 kernel/sched/cputime.c:709) > r5:8181fbb0 r4:834f0000 > [<8028ea38>] (vtime_user_enter) from [<8181fbb0>] (__context_tracking_enter+0x148/0x334 kernel/context_tracking.c:82) > r7:82a22498 r6:828ac940 r5:ffffe000 r4:00000001 > [<8181fa68>] (__context_tracking_enter) from [<80417170>] (context_tracking_enter kernel/context_tracking.c:122 [inline]) > [<8181fa68>] (__context_tracking_enter) from [<80417170>] (context_tracking_enter+0x54/0x84 kernel/context_tracking.c:106) > r7:00000000 r6:00000000 r5:60000193 r4:00000001 > [<8041711c>] (context_tracking_enter) from [<804171bc>] (user_enter include/linux/context_tracking.h:28 [inline]) > [<8041711c>] (context_tracking_enter) from [<804171bc>] (context_tracking_user_enter+0x1c/0x20 kernel/context_tracking.c:130) > r5:81820218 r4:00000000 > [<804171a0>] (context_tracking_user_enter) from [<802000d4>] (no_work_pending+0x8/0x38) > Exception stack(0x834dffb0 to 0x834dfff8) > ffa0: 00000000 00000000 00000000 00000000 > ffc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > ffe0: 00000000 7ec68ef0 00000000 76ee5a00 00000010 00000000 > Rebooting in 86400 seconds.. > > > --- > 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. > > -- > You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group. > To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/0000000000004f14c105bde08f75%40google.com.
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Vyukov <dvyukov@google.com> To: syzbot <syzbot+f09a12b2c77bfbbf51bd@syzkaller.appspotmail.com>, Mark Rutland <mark.rutland@arm.com>, Russell King - ARM Linux <linux@armlinux.org.uk>, Arnd Bergmann <arnd@arndb.de>, Linux ARM <linux-arm-kernel@lists.infradead.org> Cc: Alexandre Chartre <alexandre.chartre@oracle.com>, LKML <linux-kernel@vger.kernel.org>, Masami Hiramatsu <mhiramat@kernel.org>, Peter Zijlstra <peterz@infradead.org>, syzkaller-bugs <syzkaller-bugs@googlegroups.com>, Thomas Gleixner <tglx@linutronix.de> Subject: Re: [syzbot] upstream boot error: WARNING in __context_tracking_enter Date: Fri, 19 Mar 2021 10:54:48 +0100 [thread overview] Message-ID: <CACT4Y+bLkFSc8manYrCukj-_nzwVsV9y6xYWXmGyYFS-PoBRPQ@mail.gmail.com> (raw) In-Reply-To: <0000000000004f14c105bde08f75@google.com> .On Fri, Mar 19, 2021 at 10:44 AM syzbot <syzbot+f09a12b2c77bfbbf51bd@syzkaller.appspotmail.com> wrote: > > Hello, > > syzbot found the following issue on: > > HEAD commit: 8b12a62a Merge tag 'drm-fixes-2021-03-19' of git://anongit.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=17e815aed00000 > kernel config: https://syzkaller.appspot.com/x/.config?x=cfeed364fc353c32 > dashboard link: https://syzkaller.appspot.com/bug?extid=f09a12b2c77bfbbf51bd > userspace arch: arm > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+f09a12b2c77bfbbf51bd@syzkaller.appspotmail.com +Mark, arm It did not get far with CONFIG_CONTEXT_TRACKING_FORCE (kernel doesn't boot). > Run /sbin/init as init process > ------------[ cut here ]------------ > WARNING: CPU: 0 PID: 1 at include/linux/seqlock.h:271 __seqprop_assert include/linux/seqlock.h:271 [inline] > WARNING: CPU: 0 PID: 1 at include/linux/seqlock.h:271 __seqprop_assert.constprop.0+0xf0/0x11c include/linux/seqlock.h:269 > Modules linked in: > Kernel panic - not syncing: panic_on_warn set ... > CPU: 0 PID: 1 Comm: init Not tainted 5.12.0-rc3-syzkaller #0 > Hardware name: ARM-Versatile Express > Backtrace: > [<81804310>] (dump_backtrace) from [<81804584>] (show_stack+0x18/0x1c arch/arm/kernel/traps.c:252) > r7:00000080 r6:60000193 r5:00000000 r4:82b58444 > [<8180456c>] (show_stack) from [<8180bc58>] (__dump_stack lib/dump_stack.c:79 [inline]) > [<8180456c>] (show_stack) from [<8180bc58>] (dump_stack+0xb8/0xe8 lib/dump_stack.c:120) > [<8180bba0>] (dump_stack) from [<81805118>] (panic+0x130/0x378 kernel/panic.c:231) > r7:81f487d4 r6:82a390e4 r5:00000000 r4:82c6b0d8 > [<81804fe8>] (panic) from [<802447b4>] (__warn+0xb0/0x164 kernel/panic.c:605) > r3:82a2248c r2:00000000 r1:5b71e000 r0:81f487d4 > r7:0000010f > [<80244704>] (__warn) from [<818053c8>] (warn_slowpath_fmt+0x68/0xd4 kernel/panic.c:628) > r7:8028c4b4 r6:0000010f r5:81f40c30 r4:00000000 > [<81805364>] (warn_slowpath_fmt) from [<8028c4b4>] (__seqprop_assert include/linux/seqlock.h:271 [inline]) > [<81805364>] (warn_slowpath_fmt) from [<8028c4b4>] (__seqprop_assert.constprop.0+0xf0/0x11c include/linux/seqlock.h:269) > r8:00000000 r7:82a22498 r6:828ac940 r5:8181fbb0 r4:00000001 > [<8028c3c4>] (__seqprop_assert.constprop.0) from [<8028ea54>] (vtime_user_enter+0x1c/0x90 kernel/sched/cputime.c:709) > r5:8181fbb0 r4:834f0000 > [<8028ea38>] (vtime_user_enter) from [<8181fbb0>] (__context_tracking_enter+0x148/0x334 kernel/context_tracking.c:82) > r7:82a22498 r6:828ac940 r5:ffffe000 r4:00000001 > [<8181fa68>] (__context_tracking_enter) from [<80417170>] (context_tracking_enter kernel/context_tracking.c:122 [inline]) > [<8181fa68>] (__context_tracking_enter) from [<80417170>] (context_tracking_enter+0x54/0x84 kernel/context_tracking.c:106) > r7:00000000 r6:00000000 r5:60000193 r4:00000001 > [<8041711c>] (context_tracking_enter) from [<804171bc>] (user_enter include/linux/context_tracking.h:28 [inline]) > [<8041711c>] (context_tracking_enter) from [<804171bc>] (context_tracking_user_enter+0x1c/0x20 kernel/context_tracking.c:130) > r5:81820218 r4:00000000 > [<804171a0>] (context_tracking_user_enter) from [<802000d4>] (no_work_pending+0x8/0x38) > Exception stack(0x834dffb0 to 0x834dfff8) > ffa0: 00000000 00000000 00000000 00000000 > ffc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > ffe0: 00000000 7ec68ef0 00000000 76ee5a00 00000010 00000000 > Rebooting in 86400 seconds.. > > > --- > 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. > > -- > You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group. > To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/0000000000004f14c105bde08f75%40google.com. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-19 9:55 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-19 9:44 [syzbot] upstream boot error: WARNING in __context_tracking_enter syzbot 2021-03-19 9:54 ` Dmitry Vyukov [this message] 2021-03-19 9:54 ` Dmitry Vyukov 2021-03-19 10:10 ` Russell King - ARM Linux admin 2021-03-19 10:10 ` Russell King - ARM Linux admin 2021-03-22 17:22 ` Mark Rutland 2021-03-22 17:22 ` Mark Rutland 2021-04-13 5:14 ` Dmitry Vyukov 2021-04-13 5:14 ` Dmitry Vyukov 2021-11-10 9:08 ` Marco Elver 2021-11-10 9:08 ` Marco Elver
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=CACT4Y+bLkFSc8manYrCukj-_nzwVsV9y6xYWXmGyYFS-PoBRPQ@mail.gmail.com \ --to=dvyukov@google.com \ --cc=alexandre.chartre@oracle.com \ --cc=arnd@arndb.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=mark.rutland@arm.com \ --cc=mhiramat@kernel.org \ --cc=peterz@infradead.org \ --cc=syzbot+f09a12b2c77bfbbf51bd@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.