All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+7535c916093a64efc0d2@syzkaller.appspotmail.com>
To: frederic@kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: [syzbot] upstream boot error: WARNING in vtime_user_enter
Date: Fri, 05 Nov 2021 15:52:26 -0700	[thread overview]
Message-ID: <0000000000003e37cb05d0127f04@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    fe91c4725aee Merge tag 'scsi-misc' of git://git.kernel.org..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12651382b00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=788cf6fa2a42d474
dashboard link: https://syzkaller.appspot.com/bug?extid=7535c916093a64efc0d2
compiler:       arm-linux-gnueabi-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1
userspace arch: arm

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

Registered RDS/tcp transport
NET: Registered PF_SMC protocol family
9pnet: Installing 9P2000 support
Key type dns_resolver registered
Key type ceph registered
libceph: loaded (mon/osd proto 15/24)
NET: Registered PF_VSOCK protocol family
Registering SWP/SWPB emulation handler
registered taskstats version 1
Loading compiled-in X.509 certificates
Loaded X.509 cert 'Build time autogenerated kernel key: f850c787ad998c396ae089c083b940ff0a9abb77'
zswap: loaded using pool lzo/zbud
Key type ._fscrypt registered
Key type .fscrypt registered
Key type fscrypt-provisioning registered
Key type big_key registered
Key type encrypted registered
ima: No TPM chip found, activating TPM-bypass!
Loading compiled-in module X.509 certificates
Loaded X.509 cert 'Build time autogenerated kernel key: f850c787ad998c396ae089c083b940ff0a9abb77'
ima: Allocated hash algorithm: sha256
ima: No architecture policies found
evm: Initialising EVM extended attributes:
evm: security.selinux
evm: security.SMACK64 (disabled)
evm: security.SMACK64EXEC (disabled)
evm: security.SMACK64TRANSMUTE (disabled)
evm: security.SMACK64MMAP (disabled)
evm: security.apparmor (disabled)
evm: security.ima
evm: security.capability
evm: HMAC attrs: 0x1
printk: console [netcon0] enabled
netconsole: network logging started
gtp: GTP module loaded (pdp ctx size 64 bytes)
ALSA device list:
  #0: Dummy 1
  #1: Loopback 1
  #2: Virtual MIDI Card 1
  #3: ARM AC'97 Interface PL041 rev0 at 0x1c040000, irq 36
uart-pl011 1c090000.serial: no DMA platform data
md: Skipping autodetection of RAID arrays. (raid=autodetect will force)
EXT4-fs (vda): mounted filesystem without journal. Opts: (null). Quota mode: none.
VFS: Mounted root (ext4 filesystem) readonly on device 253:0.
devtmpfs: mounted
Freeing unused kernel image (initmem) memory: 2048K
Failed to set sysctl parameter 'vm.nr_hugepages=4': parameter not found
Failed to set sysctl parameter 'vm.nr_overcommit_hugepages=4': parameter not found
Run /sbin/init as init process
------------[ cut here ]------------
WARNING: CPU: 1 PID: 1 at include/linux/seqlock.h:271 __seqprop_assert include/linux/seqlock.h:271 [inline]
WARNING: CPU: 1 PID: 1 at include/linux/seqlock.h:271 __seqprop_assert include/linux/seqlock.h:269 [inline]
WARNING: CPU: 1 PID: 1 at include/linux/seqlock.h:271 vtime_user_enter+0x13c/0x140 kernel/sched/cputime.c:709
Modules linked in:
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 1 Comm: init Not tainted 5.15.0-syzkaller #0
Hardware name: ARM-Versatile Express
Backtrace: 
[<818473a0>] (dump_backtrace) from [<81847728>] (show_stack+0x18/0x1c arch/arm/kernel/traps.c:237)
 r7:81f6ac1c r6:00000080 r5:81f7ca6c r4:60000093
[<81847710>] (show_stack) from [<81851734>] (__dump_stack lib/dump_stack.c:88 [inline])
[<81847710>] (show_stack) from [<81851734>] (dump_stack_lvl+0x70/0x98 lib/dump_stack.c:106)
[<818516c4>] (dump_stack_lvl) from [<81851774>] (dump_stack+0x18/0x1c lib/dump_stack.c:113)
 r7:81f6ac1c r6:82639b0c r5:00000000 r4:82878098
[<8185175c>] (dump_stack) from [<81848284>] (panic+0x114/0x354 kernel/panic.c:232)
[<81848170>] (panic) from [<802437d8>] (__warn+0xa4/0x13c kernel/panic.c:603)
 r3:82622488 r2:00000000 r1:838d7cd8 r0:81f6ac1c
 r7:00000009
[<80243734>] (__warn) from [<8184852c>] (warn_slowpath_fmt+0x68/0xd4 kernel/panic.c:626)
 r8:00000009 r7:8028e1ac r6:0000010f r5:81f62fd0 r4:00000000
[<818484c8>] (warn_slowpath_fmt) from [<8028e1ac>] (__seqprop_assert include/linux/seqlock.h:271 [inline])
[<818484c8>] (warn_slowpath_fmt) from [<8028e1ac>] (__seqprop_assert include/linux/seqlock.h:269 [inline])
[<818484c8>] (warn_slowpath_fmt) from [<8028e1ac>] (vtime_user_enter+0x13c/0x140 kernel/sched/cputime.c:709)
 r8:82622494 r7:00000001 r6:838e0710 r5:81864e90 r4:838e0000
[<8028e070>] (vtime_user_enter) from [<81864e90>] (__context_tracking_enter+0xf8/0x25c kernel/context_tracking.c:82)
 r7:00000001 r6:838e0000 r5:824a7bc8 r4:00000001
[<81864d98>] (__context_tracking_enter) from [<8041bbbc>] (context_tracking_enter kernel/context_tracking.c:122 [inline])
[<81864d98>] (__context_tracking_enter) from [<8041bbbc>] (context_tracking_enter+0x4c/0x7c kernel/context_tracking.c:106)
 r9:838e0000 r8:00000000 r7:00000000 r6:00000000 r5:60000093 r4:00000001
[<8041bb70>] (context_tracking_enter) from [<8041bc84>] (user_enter include/linux/context_tracking.h:28 [inline])
[<8041bb70>] (context_tracking_enter) from [<8041bc84>] (context_tracking_user_enter+0x1c/0x20 kernel/context_tracking.c:130)
 r5:818654dc r4:00000000
[<8041bc68>] (context_tracking_user_enter) from [<802000b4>] (no_work_pending+0x8/0x44)
Exception stack(0x838d7fb0 to 0x838d7ff8)
7fa0:                                     00000000 00000000 00000000 00000000
7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
7fe0: 00000000 7eb28ed0 00000000 76f66a00 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.

                 reply	other threads:[~2021-11-05 22:52 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=0000000000003e37cb05d0127f04@google.com \
    --to=syzbot+7535c916093a64efc0d2@syzkaller.appspotmail.com \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    /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 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.