Messages in this thread | | | From | Dmitry Vyukov <> | Date | Tue, 2 May 2023 08:49:27 +0200 | Subject | Re: [syzbot] upstream boot error: Internal error in corrupted |
| |
On Fri, 28 Apr 2023 at 23:46, syzbot <syzbot+b94704ab726aaea4a3a3@syzkaller.appspotmail.com> wrote: > > Hello, > > syzbot found the following issue on: > > HEAD commit: 6e98b09da931 Merge tag 'net-next-6.4' of git://git.kernel... > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=13053240280000 > kernel config: https://syzkaller.appspot.com/x/.config?x=5d0e7ab221001b97 > dashboard link: https://syzkaller.appspot.com/bug?extid=b94704ab726aaea4a3a3 > compiler: arm-linux-gnueabi-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 > userspace arch: arm > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+b94704ab726aaea4a3a3@syzkaller.appspotmail.com
+arm mailing list
Kernel started falling apart on arm during boot in various strange ways.
#syz set subsystems: arm
> Initmem setup node 0 [mem 0x0000000080000000-0x00000000ffffffff] > percpu: Embedded 18 pages/cpu s44168 r8192 d21368 u73728 > Built 1 zonelists, mobility grouping on. Total pages: 520868 > Kernel command line: root=/dev/vda console=ttyAMA0 earlyprintk=serial net.ifnames=0 sysctl.kernel.hung_task_all_cpu_backtrace=1 ima_policy=tcb nf-conntrack-ftp.ports=20000 nf-conntrack-tftp.ports=20000 nf-conntrack-sip.ports=20000 nf-conntrack-irc.ports=20000 nf-conntrack-sane.ports=20000 binder.debug_mask=0 rcupdate.rcu_expedited=1 rcupdate.rcu_cpu_stall_cputime=1 no_hash_pointers page_owner=on sysctl.vm.nr_hugepages=4 sysctl.vm.nr_overcommit_hugepages=4 secretmem.enable=1 sysctl.max_rcu_stall_to_panic=1 msr.allow_writes=off coredump_filter=0xffff root=/dev/vda console=ttyAMA0 vmalloc=512M smp.csd_lock_timeout=300000 watchdog_thresh=165 workqueue.watchdog_thresh=420 sysctl.net.core.netdev_unregister_timeout_secs=420 dummy_hcd.num=2 panic_on_warn=1 > Unknown kernel command line parameters "earlyprintk=serial page_owner=on", will be passed to user space. > Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes, linear) > Inode-cache hash table entries: 131072 (order: 7, 524288 bytes, linear) > allocated 2097152 bytes of page_ext > mem auto-init: stack:off, heap alloc:on, heap free:off > software IO TLB: area num 2. > software IO TLB: mapped [mem 0x00000000d9a49000-0x00000000dda49000] (64MB) > Memory: 1954376K/2097152K available (22528K kernel code, 2360K rwdata, 8380K rodata, 2048K init, 868K bss, 126392K reserved, 16384K cma-reserved, 524288K highmem) > SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 > trace event string verifier disabled > rcu: Preemptible hierarchical RCU implementation. > rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2. > rcu: RCU callback double-/use-after-free debug is enabled. > All grace periods are expedited (rcu_expedited). > Trampoline variant of Tasks RCU enabled. > Tracing variant of Tasks RCU enabled. > rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. > rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 > NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 > GIC physical location is 0x2c001000 > rcu: srcu_init: Setting srcu_struct sizes based on contention. > sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns > clocksource: arm,sp804: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns > arch_timer: cp15 timer(s) running at 62.50MHz (virt). > clocksource: arch_sys_counter: mask: 0x1ffffffffffffff max_cycles: 0x1cd42e208c, max_idle_ns: 881590405314 ns > sched_clock: 57 bits at 63MHz, resolution 16ns, wraps every 4398046511096ns > Switching to timer-based delay loop, resolution 16ns > Console: colour dummy device 80x30 > Calibrating delay loop (skipped), value calculated using timer frequency.. 125.00 BogoMIPS (lpj=625000) > pid_max: default: 32768 minimum: 301 > LSM: initializing lsm=lockdown,capability,landlock,yama,safesetid,tomoyo,selinux,bpf,integrity > landlock: Up and running. > Yama: becoming mindful. > TOMOYO Linux initialized > SELinux: Initializing. > LSM support for eBPF active > stackdepot: allocating hash table of 131072 entries via kvcalloc > Mount-cache hash table entries: 4096 (order: 2, 16384 bytes, linear) > Mountpoint-cache hash table entries: 4096 (order: 2, 16384 bytes, linear) > CPU: Testing write buffer coherency: ok > CPU0: Spectre BHB: enabling loop workaround for all CPUs > CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 > Insufficient stack space to handle exception! > Task stack: [0xdf85c000..0xdf85e000] > IRQ stack: [0xdf804000..0xdf806000] > Overflow stack: [0x82a14000..0x82a15000] > Internal error: kernel stack overflow: 0 [#1] PREEMPT SMP ARM > Modules linked in: > CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.3.0-syzkaller #0 > Hardware name: ARM-Versatile Express > PC is at 0x0 > LR is at debug_smp_processor_id+0x20/0x24 lib/smp_processor_id.c:60 > pc : [<00000000>] lr : [<817ec4c8>] psr: 20000193 > sp : 00000000 ip : df805f80 fp : 00000000 > r10: 825e0afd r9 : 828fb980 r8 : 00000000 > r7 : 00000000 r6 : 00000000 r5 : 00000000 r4 : 00000000 > r3 : 00000001 r2 : 817eb958 r1 : 81d982d4 r0 : 00000001 > Flags: nzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment none > Control: 30c5387d Table: 80003000 DAC: 00000000 > Register r0 information: non-paged memory > Register r1 information: non-slab/vmalloc memory > Register r2 information: non-slab/vmalloc memory > Register r3 information: non-paged memory > Register r4 information: NULL pointer > Register r5 information: NULL pointer > Register r6 information: NULL pointer > Register r7 information: NULL pointer > Register r8 information: NULL pointer > Register r9 information: > ------------[ cut here ]------------ > WARNING: CPU: 1 PID: 0 at mm/slub.c:4650 __kmem_obj_info+0x1c4/0x21c mm/slub.c:4650 > Modules linked in: > > > --- > 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. > > If the bug is already fixed, let syzbot know by replying with: > #syz fix: exact-commit-title > > If you want to change bug's subsystems, reply with: > #syz set subsystems: new-subsystem > (See the list of subsystem names on the web dashboard) > > If the bug is a duplicate of another bug, reply with: > #syz dup: exact-subject-of-another-report > > If you want to undo deduplication, reply with: > #syz undup > > -- > 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/00000000000025a04405fa6c69a0%40google.com.
| |