From: kernel test robot <oliver.sang@intel.com>
To: Kees Cook <kees@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, <linux-hardening@vger.kernel.org>,
<kasan-dev@googlegroups.com>, <linux-kbuild@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [linus:master] [ubsan/overflow] ed2b548f10: INFO:task_blocked_for_more_than#seconds
Date: Wed, 23 Apr 2025 15:18:40 +0800 [thread overview]
Message-ID: <202504231437.d0a0174e-lkp@intel.com> (raw)
Hello,
we don't have enough knowledge to dig deep the relation between the random
issues and the change. we tried to rebuild kernel. still see the same config
diff:
--- /pkg/linux/i386-randconfig-013-20250413/gcc-12/d2cf8ccf5a1871058a083c00efe37d7eb91bf6bd/.config 2025-04-22 15:01:12.846009313 +0800
+++ /pkg/linux/i386-randconfig-013-20250413/gcc-12/ed2b548f1017586c44f50654ef9febb42d491f31/.config 2025-04-22 15:00:23.620141366 +0800
@@ -5558,7 +5558,6 @@ CONFIG_UBSAN_BOUNDS_STRICT=y
CONFIG_UBSAN_SHIFT=y
# CONFIG_UBSAN_DIV_ZERO is not set
CONFIG_UBSAN_UNREACHABLE=y
-CONFIG_UBSAN_SIGNED_WRAP=y
# CONFIG_UBSAN_BOOL is not set
# CONFIG_UBSAN_ENUM is not set
# CONFIG_UBSAN_ALIGNMENT is not set
we tried run both parent and this commit until almost 1000 times, the parent
still keep clean on running same test, this commit shows various issues
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/runtime/scale_type:
vm-snb-i386/rcuscale/debian-11.1-i386-20220923.cgz/i386-randconfig-013-20250413/gcc-12/300s/srcu
d2cf8ccf5a187105 ed2b548f1017586c44f50654ef9
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:999 27% 269:998 last_state.booting
:999 27% 269:998 last_state.is_incomplete_run
:999 18% 177:998 dmesg.BUG:kernel_hang_in_boot_stage
:999 2% 16:998 dmesg.BUG:workqueue_lockup-pool
:999 18% 176:998 dmesg.INFO:task_blocked_for_more_than#seconds
:999 8% 76:998 dmesg.IP-Config:Auto-configuration_of_network_failed
:999 27% 269:998 dmesg.boot_failures
so we still make out this report FYI what we observed in our tests.
kernel test robot noticed "INFO:task_blocked_for_more_than#seconds" on:
commit: ed2b548f1017586c44f50654ef9febb42d491f31 ("ubsan/overflow: Rework integer overflow sanitizer option to turn on everything")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master c1336865c4c90fcc649df0435a7c86c30030a723]
[test failed on linux-next/master f660850bc246fef15ba78c81f686860324396628]
in testcase: rcuscale
version:
with following parameters:
runtime: 300s
scale_type: srcu
config: i386-randconfig-013-20250413
compiler: gcc-12
test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202504231437.d0a0174e-lkp@intel.com
[ 985.037272][ T22] INFO: task swapper:1 blocked for more than 491 seconds.
[ 985.037272][ T22] Tainted: G T 6.14.0-rc2-00021-ged2b548f1017 #1
[ 985.114644][ T22] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 985.131238][ T22] task:swapper state:D stack:0 pid:1 tgid:1 ppid:0 task_flags:0x4000040 flags:0x00004000
[ 985.184178][ T22] Call Trace:
[ 985.184178][ T22] __schedule (kernel/sched/core.c:5380 kernel/sched/core.c:6764)
[ 985.239369][ T22] schedule (kernel/sched/core.c:6842 kernel/sched/core.c:6856)
[ 985.292955][ T22] async_synchronize_cookie_domain (kernel/async.c:317 kernel/async.c:310)
[ 985.292955][ T22] ? swake_up_all (kernel/sched/wait.c:383)
[ 985.347537][ T22] wait_for_initramfs (init/initramfs.c:767)
[ 985.347537][ T22] populate_rootfs (init/initramfs.c:777)
[ 985.402751][ T22] ? do_copy (init/initramfs.c:771)
[ 985.402751][ T22] do_one_initcall (init/main.c:1257)
[ 985.483184][ T22] ? parse_args (kernel/params.c:188)
[ 985.536816][ T22] do_initcalls (init/main.c:1318 init/main.c:1335)
[ 985.599031][ T22] kernel_init_freeable (init/main.c:1570)
[ 985.599031][ T22] ? rest_init (init/main.c:1449)
[ 985.625998][ T22] kernel_init (init/main.c:1459)
[ 985.625998][ T22] ret_from_fork (arch/x86/kernel/process.c:154)
[ 985.680001][ T22] ? rest_init (init/main.c:1449)
[ 985.680001][ T22] ret_from_fork_asm (arch/x86/entry/entry_32.S:737)
[ 985.733799][ T22] entry_INT80_32 (arch/x86/entry/entry_32.S:942)
[ 985.842056][ T22]
[ 985.842056][ T22] Showing all locks held in the system:
[ 985.842056][ T22] 4 locks held by kworker/u4:1/19:
[ 985.895824][ T22] 1 lock held by khungtaskd/22:
[ 985.895824][ T22] #0: c88799b0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire (include/linux/rcupdate.h:336)
[ 985.949551][ T22]
[ 985.949551][ T22] =============================================
[ 985.949551][ T22]
BUG: kernel hang in boot stage
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250423/202504231437.d0a0174e-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-23 7:18 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=202504231437.d0a0174e-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=kasan-dev@googlegroups.com \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/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.