[ptrace] 201766a20e: kernel_selftests.seccomp.make_fail
by kernel test robot
FYI, we noticed the following commit (built with gcc-7):
commit: 201766a20e30f982ccfe36bebfad9602c3ff574a ("ptrace: add PTRACE_GET_SYSCALL_INFO request")
https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git master
in testcase: kernel_selftests
with following parameters:
group: kselftests-02
test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 8G
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <rong.a.chen(a)intel.com>
2019-07-26 16:52:03 make run_tests -C seccomp
make: Entering directory '/usr/src/perf_selftests-x86_64-rhel-7.6-201766a20e30f982ccfe36bebfad9602c3ff574a/tools/testing/selftests/seccomp'
gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf
In file included from seccomp_bpf.c:51:0:
seccomp_bpf.c: In function ‘tracer_ptrace’:
seccomp_bpf.c:1787:20: error: ‘PTRACE_EVENTMSG_SYSCALL_ENTRY’ undeclared (first use in this function)
EXPECT_EQ(entry ? PTRACE_EVENTMSG_SYSCALL_ENTRY
^
../kselftest_harness.h:608:13: note: in definition of macro ‘__EXPECT’
__typeof__(_expected) __exp = (_expected); \
^~~~~~~~~
seccomp_bpf.c:1787:2: note: in expansion of macro ‘EXPECT_EQ’
EXPECT_EQ(entry ? PTRACE_EVENTMSG_SYSCALL_ENTRY
^~~~~~~~~
seccomp_bpf.c:1787:20: note: each undeclared identifier is reported only once for each function it appears in
EXPECT_EQ(entry ? PTRACE_EVENTMSG_SYSCALL_ENTRY
^
../kselftest_harness.h:608:13: note: in definition of macro ‘__EXPECT’
__typeof__(_expected) __exp = (_expected); \
^~~~~~~~~
seccomp_bpf.c:1787:2: note: in expansion of macro ‘EXPECT_EQ’
EXPECT_EQ(entry ? PTRACE_EVENTMSG_SYSCALL_ENTRY
^~~~~~~~~
seccomp_bpf.c:1788:6: error: ‘PTRACE_EVENTMSG_SYSCALL_EXIT’ undeclared (first use in this function)
: PTRACE_EVENTMSG_SYSCALL_EXIT, msg);
^
../kselftest_harness.h:608:13: note: in definition of macro ‘__EXPECT’
__typeof__(_expected) __exp = (_expected); \
^~~~~~~~~
seccomp_bpf.c:1787:2: note: in expansion of macro ‘EXPECT_EQ’
EXPECT_EQ(entry ? PTRACE_EVENTMSG_SYSCALL_ENTRY
^~~~~~~~~
Makefile:12: recipe for target 'seccomp_bpf' failed
make: *** [seccomp_bpf] Error 1
make: Leaving directory '/usr/src/perf_selftests-x86_64-rhel-7.6-201766a20e30f982ccfe36bebfad9602c3ff574a/tools/testing/selftests/seccomp'
To reproduce:
# build kernel
cd linux
cp config-5.2.0-10889-g201766a20e30f9 .config
make HOSTCC=gcc-7 CC=gcc-7 ARCH=x86_64 olddefconfig prepare modules_prepare bzImage
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email
Thanks,
Rong Chen
5 months, 3 weeks
[random32] b4ad8182a9: BUG:using__this_cpu_read()in_preemptible[#]code:swapper
by kernel test robot
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: b4ad8182a9a6cadba67b7441e9294486b43df30e ("random32: add noise from network and scheduling activity")
https://git.kernel.org/cgit/linux/kernel/git/wtarreau/prandom.git 20200901-siphash-noise
in testcase: boot
on test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 8G
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
+----------------------------------------------------------+------------+------------+
| | f6be36dddf | b4ad8182a9 |
+----------------------------------------------------------+------------+------------+
| boot_successes | 6 | 0 |
| boot_failures | 0 | 7 |
| BUG:using__this_cpu_read()in_preemptible[#]code:swapper | 0 | 7 |
| BUG:using__this_cpu_write()in_preemptible[#]code:swapper | 0 | 7 |
+----------------------------------------------------------+------------+------------+
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <lkp(a)intel.com>
[ 9.056198] BUG: using __this_cpu_read() in preemptible [00000000] code: swapper/0/1
[ 9.057934] caller is __this_cpu_preempt_check+0xf/0x11
[ 9.058992] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.9.0-rc3-00002-gb4ad8182a9a6ca #1
[ 9.060712] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
[ 9.061912] Call Trace:
[ 9.061912] dump_stack+0x54/0x6e
[ 9.061912] check_preemption_disabled+0xb1/0xc0
[ 9.061912] __this_cpu_preempt_check+0xf/0x11
[ 9.065516] __igt_reserve+0x91/0x580
[ 9.065516] igt_reserve+0x5b/0xc0
[ 9.065516] test_drm_mm_init+0x78/0xa9
[ 9.065516] ? drm_kms_helper_init+0xa/0xa
[ 9.065516] do_one_initcall+0x34/0x12f
[ 9.069409] ? parse_args+0xf0/0x280
[ 9.069409] ? do_initcalls+0x7c/0xc4
[ 9.069409] do_initcalls+0xa1/0xc4
[ 9.069409] kernel_init_freeable+0x88/0xb2
[ 9.069409] ? rest_init+0xfd/0xfd
[ 9.073368] kernel_init+0x8/0xe3
[ 9.073368] ret_from_fork+0x19/0x24
To reproduce:
# build kernel
cd linux
cp config-5.9.0-rc3-00002-gb4ad8182a9a6ca .config
make HOSTCC=gcc-9 CC=gcc-9 ARCH=i386 olddefconfig prepare modules_prepare bzImage
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email
Thanks,
lkp
5 months, 3 weeks
[block] 08fc1ab6d7: mdadm-selftests./lkp/benchmarks/mdadm-selftests/tests/12imsm-r0_2d-grow-r0_3d.fail
by kernel test robot
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: 08fc1ab6d748ab1a690fd483f41e2938984ce353 ("block: fix locking in bdev_del_partition")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: mdadm-selftests
version: mdadm-selftests-x86_64-5d518de-1_20200717
with following parameters:
disk: 1HDD
test_prefix: 12
ucode: 0x21
on test machine: 4 threads Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz with 4G memory
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <rong.a.chen(a)intel.com>
2020-09-07 20:24:22 mkdir -p /var/tmp
2020-09-07 20:24:22 mke2fs -t ext3 -b 4096 -J size=4 -q /dev/sda3
2020-09-07 20:25:24 mount -t ext3 /dev/sda3 /var/tmp
sed -e 's/{DEFAULT_METADATA}/1.2/g' \
-e 's,{MAP_PATH},/run/mdadm/map,g' mdadm.8.in > mdadm.8
/usr/bin/install -D -m 644 mdadm.8 /usr/share/man/man8/mdadm.8
/usr/bin/install -D -m 644 mdmon.8 /usr/share/man/man8/mdmon.8
/usr/bin/install -D -m 644 md.4 /usr/share/man/man4/md.4
/usr/bin/install -D -m 644 mdadm.conf.5 /usr/share/man/man5/mdadm.conf.5
/usr/bin/install -D -m 644 udev-md-raid-creating.rules /lib/udev/rules.d/01-md-raid-creating.rules
/usr/bin/install -D -m 644 udev-md-raid-arrays.rules /lib/udev/rules.d/63-md-raid-arrays.rules
/usr/bin/install -D -m 644 udev-md-raid-assembly.rules /lib/udev/rules.d/64-md-raid-assembly.rules
/usr/bin/install -D -m 644 udev-md-clustered-confirm-device.rules /lib/udev/rules.d/69-md-clustered-confirm-device.rules
/usr/bin/install -D -m 755 mdadm /sbin/mdadm
/usr/bin/install -D -m 755 mdmon /sbin/mdmon
Testing on linux-5.9.0-rc1-00053-g08fc1ab6d748a kernel
/lkp/benchmarks/mdadm-selftests/tests/12imsm-r0_2d-grow-r0_3d... FAILED - see /var/tmp/12imsm-r0_2d-grow-r0_3d.log and /var/tmp/fail12imsm-r0_2d-grow-r0_3d.log for details
12imsm-r0_2d-grow-r0_3d TIMEOUT
Testing on linux-5.9.0-rc1-00053-g08fc1ab6d748a kernel
/lkp/benchmarks/mdadm-selftests/tests/12imsm-r0_2d-grow-r0_4d... FAILED - see /var/tmp/12imsm-r0_2d-grow-r0_4d.log and /var/tmp/fail12imsm-r0_2d-grow-r0_4d.log for details
12imsm-r0_2d-grow-r0_4d TIMEOUT
Testing on linux-5.9.0-rc1-00053-g08fc1ab6d748a kernel
/lkp/benchmarks/mdadm-selftests/tests/12imsm-r0_2d-grow-r0_5d... FAILED - see /var/tmp/12imsm-r0_2d-grow-r0_5d.log and /var/tmp/fail12imsm-r0_2d-grow-r0_5d.log for details
12imsm-r0_2d-grow-r0_5d TIMEOUT
Testing on linux-5.9.0-rc1-00053-g08fc1ab6d748a kernel
/lkp/benchmarks/mdadm-selftests/tests/12imsm-r0_3d-grow-r0_4d... FAILED - see /var/tmp/12imsm-r0_3d-grow-r0_4d.log and /var/tmp/fail12imsm-r0_3d-grow-r0_4d.log for details
12imsm-r0_3d-grow-r0_4d TIMEOUT
Testing on linux-5.9.0-rc1-00053-g08fc1ab6d748a kernel
/lkp/benchmarks/mdadm-selftests/tests/12imsm-r5_3d-grow-r5_4d... FAILED - see /var/tmp/12imsm-r5_3d-grow-r5_4d.log and /var/tmp/fail12imsm-r5_3d-grow-r5_4d.log for details
12imsm-r5_3d-grow-r5_4d TIMEOUT
Testing on linux-5.9.0-rc1-00053-g08fc1ab6d748a kernel
/lkp/benchmarks/mdadm-selftests/tests/12imsm-r5_3d-grow-r5_5d... FAILED - see /var/tmp/12imsm-r5_3d-grow-r5_5d.log and /var/tmp/fail12imsm-r5_3d-grow-r5_5d.log for details
12imsm-r5_3d-grow-r5_5d TIMEOUT
To reproduce:
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
Thanks,
Rong Chen
5 months, 3 weeks
[x86/sev] 77489d595c: System_halted
by kernel test robot
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: 77489d595ceee964c3ea55234942845bfe0965f5 ("x86/sev-es: Setup early #VC handler")
https://git.kernel.org/cgit/linux/kernel/git/joro/linux.git sev-es-client-tip-5.9
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 8G
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
+----------------+------------+------------+
| | 5ec01643f4 | 77489d595c |
+----------------+------------+------------+
| boot_successes | 4 | 0 |
| boot_failures | 0 | 4 |
| System_halted | 0 | 4 |
+----------------+------------+------------+
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <lkp(a)intel.com>
pages->pgt_buf_offset: 0x000000000000d000
pages->pgt_buf_size: 0x000000000000d000
Error: kernel_ident_mapping_init() failed
-- System haltedBUG: kernel hang in boot stage
Linux version 5.9.0-rc4-00249-g77489d595ceee9 #1
Command line: ip=::::vm-snb-160::dhcp root=/dev/ram0 user=lkp job=/lkp/jobs/scheduled/vm-snb-160/boot-1-yocto-x86_64-minimal-20190520.cgz-77489d595ceee964c3ea55234942845bfe0965f5-20200908-2908-8dyro0-3.yaml ARCH=x86_64 kconfig=x86_64-randconfig-a002-20200907 branch=joro/sev-es-client-tip-5.9 commit=77489d595ceee964c3ea55234942845bfe0965f5 BOOT_IMAGE=/pkg/linux/x86_64-randconfig-a002-20200907/gcc-9/77489d595ceee964c3ea55234942845bfe0965f5/vmlinuz-5.9.0-rc4-00249-g77489d595ceee9 max_uptime=600 RESULT_ROOT=/result/boot/1/vm-snb/yocto-x86_64-minimal-20190520.cgz/x86_64-randconfig-a002-20200907/gcc-9/77489d595ceee964c3ea55234942845bfe0965f5/3 LKP_SERVER=inn selinux=0 debug apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 net.ifnames=0 printk.devkmsg=on panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 prompt_ramdisk=0 drbd.minor_count=8 systemd.log_level=err ignore_loglevel console=tty0 earlyprintk=ttyS0,115200 console=ttyS0,115200 vga=normal rw rcuperf.shutdown=0 watchdog_thresh=60
Kboot worker: lkp-worker15
Elapsed time: 1020
To reproduce:
# build kernel
cd linux
cp config-5.9.0-rc4-00249-g77489d595ceee9 .config
make HOSTCC=gcc-9 CC=gcc-9 ARCH=x86_64 olddefconfig prepare modules_prepare bzImage
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email
Thanks,
lkp
5 months, 3 weeks
[ARM] d250e1290c: WARNING:at_include/linux/thread_info.h:#do_semtimedop
by kernel test robot
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: d250e1290cc53cbe59e259053543dfdbf3de5681 ("ARM: oabi-compat: rework sys_semtimedop emulation")
https://git.kernel.org/cgit/linux/kernel/git/arnd/playground.git arm-kill-set_fs
in testcase: trinity
version:
with following parameters:
runtime: 300s
test-description: Trinity is a linux system call fuzz tester.
test-url: http://codemonkey.org.uk/projects/trinity/
on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 8G
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
+-------------------------------------------------------+------------+------------+
| | 675d60ecfa | d250e1290c |
+-------------------------------------------------------+------------+------------+
| boot_successes | 9 | 0 |
| boot_failures | 0 | 12 |
| Mem-Info | 0 | 12 |
| WARNING:at_include/linux/thread_info.h:#do_semtimedop | 0 | 9 |
| RIP:do_semtimedop | 0 | 9 |
+-------------------------------------------------------+------------+------------+
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <rong.a.chen(a)intel.com>
[ 14.637999] trinity-main uses obsolete (PF_INET,SOCK_PACKET)
[ 14.792967] warning: process `trinity-c6' used the obsolete bdflush system call
[ 14.794466] Fix your initscripts?
[ 14.807661] trinity-c3: vmalloc: allocation failure: 25769803752 bytes, mode:0xcc0(GFP_KERNEL), nodemask=(null),cpuset=/,mems_allowed=0
[ 14.810112] CPU: 1 PID: 608 Comm: trinity-c3 Not tainted 5.9.0-rc1-00020-gd250e1290cc53 #1
[ 14.811866] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
[ 14.813587] Call Trace:
[ 14.814239] dump_stack+0x57/0x70
[ 14.815034] warn_alloc.cold+0x78/0xdc
[ 14.815882] __vmalloc_node_range+0x19b/0x260
[ 14.816822] ? __kmalloc_node+0x1f5/0x2b0
[ 14.817705] __vmalloc_node+0x3f/0x60
[ 14.818535] ? do_semtimedop+0xd4/0x110
[ 14.835463] do_semtimedop+0xd4/0x110
[ 14.836220] ? __perf_sw_event+0x54/0x90
[ 14.837014] ? handle_mm_fault+0x45b/0x8d0
[ 14.837836] ? security_capable+0x31/0x50
[ 14.838637] ? do_user_addr_fault+0x1f2/0x410
[ 14.839631] ? exit_to_user_mode_prepare+0x2d/0xf0
[ 14.840703] do_syscall_64+0x33/0x40
[ 14.841581] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 14.842694] RIP: 0033:0x463519
[ 14.843488] Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 db 59 00 00 c3 66 2e 0f 1f 84 00 00 00 00
[ 14.847266] RSP: 002b:00007ffc0a588d68 EFLAGS: 00000246 ORIG_RAX: 0000000000000041
[ 14.848978] RAX: ffffffffffffffda RBX: 0000000000000041 RCX: 0000000000463519
[ 14.850447] RDX: fffffffffffffffc RSI: 0000000000000000 RDI: 0000000000000008
[ 14.850866] futex_wake_op: trinity-c4 tries to shift op by -1; fix this program
[ 14.851894] RBP: 00007f13dfe7b000 R08: fffffffffffffff6 R09: 000000000000fff9
[ 14.851895] R10: 0000008861cbf478 R11: 0000000000000246 R12: 0000000000000002
[ 14.851896] R13: 00007f13dfe7b058 R14: 0000000001dde850 R15: 00007f13dfe7b000
[ 14.851932] Mem-Info:
[ 14.858192] active_anon:84 inactive_anon:8198 isolated_anon:0
[ 14.858192] active_file:0 inactive_file:0 isolated_file:0
[ 14.858192] unevictable:16127 dirty:0 writeback:0
[ 14.858192] slab_reclaimable:9229 slab_unreclaimable:2435
[ 14.858192] mapped:9751 shmem:6129 pagetables:431 bounce:0
[ 14.858192] free:1997779 free_pcp:970 free_cma:0
[ 14.865828] raw_sendmsg: trinity-c4 forgot to set AF_INET. Fix it!
[ 14.887738] Node 0 active_anon:336kB inactive_anon:34300kB active_file:0kB inactive_file:0kB unevictable:64740kB isolated(anon):0kB isolated(file):0kB mapped:39004kB dirty:0kB writeback:0kB shmem:24516kB writeback_tmp:0kB kernel_stack:1472kB all_unreclaimable? no
[ 14.892505] Node 0 DMA free:15900kB min:20kB low:32kB high:44kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
To reproduce:
# build kernel
cd linux
cp config-5.9.0-rc1-00020-gd250e1290cc53 .config
make HOSTCC=gcc-9 CC=gcc-9 ARCH=x86_64 olddefconfig prepare modules_prepare bzImage
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email
Thanks,
Rong Chen
5 months, 3 weeks
[fuse] 2ff3ba3472: dmesg.BUG:sleeping_function_called_from_invalid_context_at_include/linux/pagemap.h
by kernel test robot
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: 2ff3ba3472f402384adccf117b045cef2b5b0c71 ("[PATCH V2] fuse: Fix VM_BUG_ON_PAGE issue while accessing zero ref count page")
url: https://github.com/0day-ci/linux/commits/Pradeep-P-V-K/fuse-Fix-VM_BUG_ON...
base: https://git.kernel.org/cgit/linux/kernel/git/mszeredi/fuse.git for-next
in testcase: ltp
testcase version: ltp-x86_64-14c1f76-1_20200715
with following parameters:
disk: 1HDD
fs: xfs
test: syscalls_part5
ucode: 0x21
test-description: The LTP testsuite contains a collection of tools for testing the Linux kernel and related features.
test-url: http://linux-test-project.github.io/
on test machine: 8 threads Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz with 16G memory
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <rong.a.chen(a)intel.com>
user :notice: [ 370.063533] tst_test.c:1308: INFO: Testing on ntfs
user :notice: [ 370.081348] tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ntfs opts='' extra opts=''
user :notice: [ 370.086107] The partition start sector was not specified for /dev/loop0 and it could not be obtained automatically. It has been set to 0.
user :notice: [ 370.091011] The number of sectors per track was not specified for /dev/loop0 and it could not be obtained automatically. It has been set to 0.
user :notice: [ 370.095743] The number of heads was not specified for /dev/loop0 and it could not be obtained automatically. It has been set to 0.
user :notice: [ 370.100684] To boot from a device, Windows needs the 'partition start sector', the 'sectors per track' and the 'number of heads' to be set.
user :notice: [ 370.104104] Windows will not be able to boot from this device.
user :notice: [ 372.651701] safe_macros.c:754: INFO: Trying FUSE...
kern :err : [ 372.661731] BUG: sleeping function called from invalid context at include/linux/pagemap.h:519
user :notice: [ 372.661783] tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
kern :err : [ 372.663438] in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 4793, name: mount.ntfs
kern :warn : [ 372.663449] CPU: 6 PID: 4793 Comm: mount.ntfs Not tainted 5.8.0-00002-g2ff3ba3472f402 #1
kern :warn : [ 372.663450] Hardware name: /DZ77BH-55K, BIOS BHZ7710H.86A.0097.2012.1228.1346 12/28/2012
kern :warn : [ 372.669730] Call Trace:
kern :warn : [ 372.670820] dump_stack+0x57/0x80
kern :warn : [ 372.671943] ___might_sleep.cold+0x87/0x95
kern :warn : [ 372.673072] set_page_dirty_lock+0x1e/0x60
kern :warn : [ 372.674183] fuse_copy_finish+0x93/0xa0 [fuse]
kern :warn : [ 372.675277] fuse_copy_fill+0x38/0x180 [fuse]
kern :warn : [ 372.676348] fuse_copy_page+0x17c/0x280 [fuse]
kern :warn : [ 372.677420] fuse_copy_args+0xf7/0x140 [fuse]
kern :warn : [ 372.678484] fuse_dev_do_read+0x7b5/0x900 [fuse]
kern :warn : [ 372.679555] ? finish_wait+0xa0/0xa0
kern :warn : [ 372.680599] fuse_dev_read+0x5c/0xa0 [fuse]
kern :warn : [ 372.681649] new_sync_read+0x114/0x1a0
kern :warn : [ 372.682678] vfs_read+0x17e/0x1c0
kern :warn : [ 372.683698] ksys_read+0x5f/0xe0
kern :warn : [ 372.684717] do_syscall_64+0x4c/0xa0
kern :warn : [ 372.685724] entry_SYSCALL_64_after_hwframe+0x44/0xa9
kern :warn : [ 372.686740] RIP: 0033:0x7fde9b6b650e
kern :warn : [ 372.687726] Code: 48 8b 15 cd aa 00 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b6 0f 1f 80 00 00 00 00 8b 05 3a ef 00 00 85 c0 75 16 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 5a c3 66 0f 1f 84 00 00 00 00 00 41 54 49 89
kern :warn : [ 372.689977] RSP: 002b:00007ffce39842b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
kern :warn : [ 372.691098] RAX: ffffffffffffffda RBX: 0000000000000044 RCX: 00007fde9b6b650e
kern :warn : [ 372.692214] RDX: 0000000000021000 RSI: 00007fde9b2a3010 RDI: 0000000000000008
kern :warn : [ 372.693332] RBP: 0000555faeb29fe0 R08: 000000000000007f R09: 0000555faeb2a990
kern :warn : [ 372.694465] R10: 0000000000000007 R11: 0000000000000246 R12: 0000555faeb29fe0
kern :warn : [ 372.695571] R13: 0000555faeb1eb90 R14: 00007fde9b48eb00 R15: 0000000000021000
To reproduce:
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
Thanks,
Rong Chen
5 months, 3 weeks
[sched/fair] ec73240b16: aim7.jobs-per-min 2.3% improvement
by kernel test robot
Greeting,
FYI, we noticed a 2.3% improvement of aim7.jobs-per-min due to commit:
commit: ec73240b1627cddfd7cef018c7fa1c32e64a721e ("sched/fair: Ignore cache hotness for SMT migration")
https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git sched/core
in testcase: aim7
on test machine: 192 threads Cooper Lake with 128G memory
with following parameters:
disk: 4BRD_12G
md: RAID1
fs: xfs
test: sync_disk_rw
load: 300
cpufreq_governor: performance
ucode: 0x86000017
test-description: AIM7 is a traditional UNIX system level benchmark suite which is used to test and measure the performance of multiuser system.
test-url: https://sourceforge.net/projects/aimbench/files/aim-suite7/
Details are as below:
-------------------------------------------------------------------------------------------------->
To reproduce:
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
=========================================================================================
compiler/cpufreq_governor/disk/fs/kconfig/load/md/rootfs/tbox_group/test/testcase/ucode:
gcc-9/performance/4BRD_12G/xfs/x86_64-rhel-8.3/300/RAID1/debian-10.4-x86_64-20200603.cgz/lkp-cpx-4s1/sync_disk_rw/aim7/0x86000017
commit:
5f4a1c4ea4 ("sched/topology: Mark SD_NUMA as SDF_NEEDS_GROUPS")
ec73240b16 ("sched/fair: Ignore cache hotness for SMT migration")
5f4a1c4ea44728aa ec73240b1627cddfd7cef018c7f
---------------- ---------------------------
%stddev %change %stddev
\ | \
5365 +2.3% 5488 aim7.jobs-per-min
335.52 -2.2% 327.98 aim7.time.elapsed_time
335.52 -2.2% 327.98 aim7.time.elapsed_time.max
5014 ± 2% -7.5% 4638 ± 2% aim7.time.system_time
51059388 -1.5% 50309088 aim7.time.voluntary_context_switches
49.81 ± 2% +4.0% 51.78 iostat.cpu.iowait
9.24 -4.3% 8.84 ± 2% iostat.cpu.system
0.07 ± 24% +138.0% 0.16 ± 31% sched_debug.cfs_rq:/.nr_spread_over.avg
0.20 ± 28% +77.0% 0.36 ± 22% sched_debug.cfs_rq:/.nr_spread_over.stddev
49.38 ± 2% +4.1% 51.38 vmstat.cpu.wa
223673 +2.3% 228851 vmstat.io.bo
298749 +2.1% 304962 proc-vmstat.nr_file_pages
241703 +2.8% 248552 proc-vmstat.nr_unevictable
241703 +2.8% 248552 proc-vmstat.nr_zone_unevictable
5330 -9.3% 4835 ± 2% proc-vmstat.nr_zone_write_pending
1330084 -2.3% 1298931 proc-vmstat.pgfault
1.63 -0.0 1.59 perf-stat.i.branch-miss-rate%
27.64 +0.9 28.52 perf-stat.i.cache-miss-rate%
1197 -4.3% 1146 perf-stat.i.cycles-between-cache-misses
34968537 +4.0% 36353165 perf-stat.i.node-load-misses
3229831 +4.0% 3357767 perf-stat.i.node-loads
1.63 -0.0 1.58 perf-stat.overall.branch-miss-rate%
27.72 +0.9 28.63 perf-stat.overall.cache-miss-rate%
1161 -4.8% 1105 perf-stat.overall.cycles-between-cache-misses
34868866 +4.0% 36247556 perf-stat.ps.node-load-misses
3220778 +4.0% 3348190 perf-stat.ps.node-loads
15.56 ± 3% -2.6 12.92 ± 4% perf-profile.calltrace.cycles-pp.__xfs_log_force_lsn.xfs_file_fsync.xfs_file_buffered_aio_write.new_sync_write.vfs_write
9.81 ± 4% -1.8 7.97 ± 5% perf-profile.calltrace.cycles-pp._raw_spin_lock.__xfs_log_force_lsn.xfs_file_fsync.xfs_file_buffered_aio_write.new_sync_write
9.78 ± 4% -1.8 7.95 ± 5% perf-profile.calltrace.cycles-pp.native_queued_spin_lock_slowpath._raw_spin_lock.__xfs_log_force_lsn.xfs_file_fsync.xfs_file_buffered_aio_write
5.69 ± 2% -0.8 4.91 ± 2% perf-profile.calltrace.cycles-pp.xlog_wait_on_iclog.__xfs_log_force_lsn.xfs_file_fsync.xfs_file_buffered_aio_write.new_sync_write
4.01 ± 2% -0.5 3.49 ± 2% perf-profile.calltrace.cycles-pp.remove_wait_queue.xlog_wait_on_iclog.__xfs_log_force_lsn.xfs_file_fsync.xfs_file_buffered_aio_write
3.99 ± 2% -0.5 3.47 ± 2% perf-profile.calltrace.cycles-pp._raw_spin_lock_irqsave.remove_wait_queue.xlog_wait_on_iclog.__xfs_log_force_lsn.xfs_file_fsync
3.68 ± 2% -0.4 3.29 ± 4% perf-profile.calltrace.cycles-pp.remove_wait_queue.__xfs_log_force_lsn.xfs_log_force_lsn.xfs_file_fsync.xfs_file_buffered_aio_write
3.67 ± 2% -0.4 3.28 ± 4% perf-profile.calltrace.cycles-pp._raw_spin_lock_irqsave.remove_wait_queue.__xfs_log_force_lsn.xfs_log_force_lsn.xfs_file_fsync
3.65 ± 2% -0.4 3.26 ± 4% perf-profile.calltrace.cycles-pp.native_queued_spin_lock_slowpath._raw_spin_lock_irqsave.remove_wait_queue.__xfs_log_force_lsn.xfs_log_force_lsn
5.69 -0.4 5.34 perf-profile.calltrace.cycles-pp.load_balance.newidle_balance.pick_next_task_fair.__sched_text_start.schedule
1.63 ± 3% -0.3 1.37 ± 2% perf-profile.calltrace.cycles-pp.__sched_text_start.schedule.xlog_wait_on_iclog.__xfs_log_force_lsn.xfs_file_fsync
1.64 ± 3% -0.3 1.39 ± 2% perf-profile.calltrace.cycles-pp.schedule.xlog_wait_on_iclog.__xfs_log_force_lsn.xfs_file_fsync.xfs_file_buffered_aio_write
1.52 ± 3% -0.2 1.27 ± 2% perf-profile.calltrace.cycles-pp.pick_next_task_fair.__sched_text_start.schedule.xlog_wait_on_iclog.__xfs_log_force_lsn
1.51 ± 3% -0.2 1.27 ± 2% perf-profile.calltrace.cycles-pp.newidle_balance.pick_next_task_fair.__sched_text_start.schedule.xlog_wait_on_iclog
2.89 ± 2% -0.2 2.69 ± 2% perf-profile.calltrace.cycles-pp.schedule.io_schedule.wait_on_page_bit.__filemap_fdatawait_range.file_write_and_wait_range
2.90 ± 2% -0.2 2.70 ± 2% perf-profile.calltrace.cycles-pp.io_schedule.wait_on_page_bit.__filemap_fdatawait_range.file_write_and_wait_range.xfs_file_fsync
2.89 ± 2% -0.2 2.69 ± 2% perf-profile.calltrace.cycles-pp.__sched_text_start.schedule.io_schedule.wait_on_page_bit.__filemap_fdatawait_range
2.64 ± 2% -0.2 2.44 ± 2% perf-profile.calltrace.cycles-pp.pick_next_task_fair.__sched_text_start.schedule.io_schedule.wait_on_page_bit
2.64 ± 2% -0.2 2.44 ± 2% perf-profile.calltrace.cycles-pp.newidle_balance.pick_next_task_fair.__sched_text_start.schedule.io_schedule
0.68 ± 2% +0.0 0.73 ± 2% perf-profile.calltrace.cycles-pp.schedule.schedule_timeout.wait_for_completion.__flush_work.xlog_cil_force_lsn
0.68 ± 2% +0.0 0.73 ± 2% perf-profile.calltrace.cycles-pp.schedule_timeout.wait_for_completion.__flush_work.xlog_cil_force_lsn.xfs_log_force_lsn
0.68 ± 2% +0.0 0.73 ± 2% perf-profile.calltrace.cycles-pp.__sched_text_start.schedule.schedule_timeout.wait_for_completion.__flush_work
0.69 ± 2% +0.0 0.74 ± 2% perf-profile.calltrace.cycles-pp.wait_for_completion.__flush_work.xlog_cil_force_lsn.xfs_log_force_lsn.xfs_file_fsync
0.79 +0.0 0.84 ± 2% perf-profile.calltrace.cycles-pp.__flush_work.xlog_cil_force_lsn.xfs_log_force_lsn.xfs_file_fsync.xfs_file_buffered_aio_write
1.79 ± 2% +0.1 1.88 ± 2% perf-profile.calltrace.cycles-pp.process_one_work.worker_thread.kthread.ret_from_fork
2.04 +0.1 2.14 ± 2% perf-profile.calltrace.cycles-pp.worker_thread.kthread.ret_from_fork
3.02 ± 4% +0.3 3.33 ± 3% perf-profile.calltrace.cycles-pp.native_queued_spin_lock_slowpath._raw_spin_lock_irq.md_flush_request.raid1_make_request.md_handle_request
3.08 ± 4% +0.3 3.39 ± 3% perf-profile.calltrace.cycles-pp._raw_spin_lock_irq.md_flush_request.raid1_make_request.md_handle_request.md_submit_bio
4.47 ± 3% +0.4 4.84 ± 2% perf-profile.calltrace.cycles-pp.md_flush_request.raid1_make_request.md_handle_request.md_submit_bio.submit_bio_noacct
4.62 ± 3% +0.4 4.99 ± 3% perf-profile.calltrace.cycles-pp.md_submit_bio.submit_bio_noacct.submit_bio.submit_bio_wait.blkdev_issue_flush
4.64 ± 3% +0.4 5.02 ± 3% perf-profile.calltrace.cycles-pp.submit_bio_noacct.submit_bio.submit_bio_wait.blkdev_issue_flush.xfs_file_fsync
4.55 ± 3% +0.4 4.93 ± 3% perf-profile.calltrace.cycles-pp.md_handle_request.md_submit_bio.submit_bio_noacct.submit_bio.submit_bio_wait
4.64 ± 3% +0.4 5.02 ± 3% perf-profile.calltrace.cycles-pp.submit_bio.submit_bio_wait.blkdev_issue_flush.xfs_file_fsync.xfs_file_buffered_aio_write
4.66 ± 3% +0.4 5.04 ± 3% perf-profile.calltrace.cycles-pp.submit_bio_wait.blkdev_issue_flush.xfs_file_fsync.xfs_file_buffered_aio_write.new_sync_write
4.71 ± 3% +0.4 5.10 ± 3% perf-profile.calltrace.cycles-pp.blkdev_issue_flush.xfs_file_fsync.xfs_file_buffered_aio_write.new_sync_write.vfs_write
8.29 +0.6 8.86 ± 2% perf-profile.calltrace.cycles-pp.native_queued_spin_lock_slowpath._raw_spin_lock_irqsave.remove_wait_queue.xlog_wait_on_iclog.__xfs_log_force_lsn
9.03 +0.9 9.92 perf-profile.calltrace.cycles-pp.__xfs_log_force_lsn.xfs_log_force_lsn.xfs_file_fsync.xfs_file_buffered_aio_write.new_sync_write
10.21 +0.9 11.14 perf-profile.calltrace.cycles-pp.xfs_log_force_lsn.xfs_file_fsync.xfs_file_buffered_aio_write.new_sync_write.vfs_write
4.33 ± 3% +1.1 5.42 ± 4% perf-profile.calltrace.cycles-pp._raw_spin_lock_irqsave.remove_wait_queue.xlog_wait_on_iclog.__xfs_log_force_lsn.xfs_log_force_lsn
4.34 ± 3% +1.1 5.44 ± 4% perf-profile.calltrace.cycles-pp.remove_wait_queue.xlog_wait_on_iclog.__xfs_log_force_lsn.xfs_log_force_lsn.xfs_file_fsync
4.73 ± 2% +1.1 5.88 ± 3% perf-profile.calltrace.cycles-pp.xlog_wait_on_iclog.__xfs_log_force_lsn.xfs_log_force_lsn.xfs_file_fsync.xfs_file_buffered_aio_write
24.59 ± 2% -1.7 22.84 ± 2% perf-profile.children.cycles-pp.__xfs_log_force_lsn
11.23 ± 4% -1.6 9.59 ± 4% perf-profile.children.cycles-pp._raw_spin_lock
7.45 -0.3 7.16 perf-profile.children.cycles-pp.schedule
6.76 -0.3 6.47 perf-profile.children.cycles-pp.newidle_balance
6.85 -0.3 6.57 perf-profile.children.cycles-pp.pick_next_task_fair
6.62 -0.3 6.34 perf-profile.children.cycles-pp.load_balance
7.92 -0.3 7.64 perf-profile.children.cycles-pp.__sched_text_start
2.90 ± 2% -0.2 2.70 ± 2% perf-profile.children.cycles-pp.io_schedule
0.70 ± 2% +0.0 0.74 ± 2% perf-profile.children.cycles-pp.wait_for_completion
0.79 +0.0 0.84 ± 2% perf-profile.children.cycles-pp.__flush_work
0.70 ± 2% +0.1 0.75 ± 2% perf-profile.children.cycles-pp.schedule_timeout
0.15 ± 5% +0.1 0.22 ± 4% perf-profile.children.cycles-pp.xlog_write
0.26 ± 2% +0.1 0.32 ± 3% perf-profile.children.cycles-pp.xlog_cil_push_work
0.00 ±387% +0.1 0.08 ± 9% perf-profile.children.cycles-pp.xlog_state_get_iclog_space
1.79 ± 2% +0.1 1.88 ± 2% perf-profile.children.cycles-pp.process_one_work
2.04 +0.1 2.14 ± 2% perf-profile.children.cycles-pp.worker_thread
3.22 ± 4% +0.3 3.53 ± 3% perf-profile.children.cycles-pp._raw_spin_lock_irq
10.42 +0.4 10.79 ± 2% perf-profile.children.cycles-pp.xlog_wait_on_iclog
4.48 ± 3% +0.4 4.86 ± 3% perf-profile.children.cycles-pp.md_flush_request
4.66 ± 3% +0.4 5.04 ± 3% perf-profile.children.cycles-pp.submit_bio_wait
4.71 ± 3% +0.4 5.10 ± 3% perf-profile.children.cycles-pp.blkdev_issue_flush
10.21 +0.9 11.14 perf-profile.children.cycles-pp.xfs_log_force_lsn
0.40 ± 3% -0.0 0.36 ± 3% perf-profile.self.cycles-pp.load_balance
aim7.jobs-per-min
5600 +--------------------------------------------------------------------+
|OO |
5550 |-+ |
| OO O OO O O O O |
5500 |-+O O OOO OOO OO OO OOO O O OO O OO OO O |
| OOO O O O O O O OO OO O O O O |
5450 |-+ O OO O OO OOO OO OO |
| + + O O |
5400 |-+ + :+ ++ : + ++++ O + |
|+++++++: ++:: + + +++++ ++++: ++ :++++ :: + ++ ++ +::+++ +|
5350 |++ + ++ + ++ ++ ++++++++ +++++ :: : ++ +++++++++++ ++ +:+ +:|
| + + + ++ ++ + +: + + |
5300 |-+ + + |
| |
5250 +--------------------------------------------------------------------+
[*] bisect-good sample
[O] bisect-bad sample
Disclaimer:
Results have been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Rong Chen
5 months, 3 weeks
[init] 7b81ce7cdc: Kernel_panic-not_syncing:VFS:Unable_to_mount_root_fs_on_unknown-block(#,#)
by kernel test robot
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: 7b81ce7cdcef3a3ae71eb3fb863433c646b4a2f4 ("init: fix error check in clean_path()")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: trinity
version: trinity-x86_64-af355e9-1_2019-12-03
with following parameters:
runtime: 300s
test-description: Trinity is a linux system call fuzz tester.
test-url: http://codemonkey.org.uk/projects/trinity/
on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 8G
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
+----------------------------------------------------------------------------+------------+------------+
| | 59126901f2 | 7b81ce7cdc |
+----------------------------------------------------------------------------+------------+------------+
| boot_successes | 4 | 0 |
| boot_failures | 0 | 4 |
| Kernel_panic-not_syncing:VFS:Unable_to_mount_root_fs_on_unknown-block(#,#) | 0 | 4 |
+----------------------------------------------------------------------------+------------+------------+
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <rong.a.chen(a)intel.com>
[ 20.510089] #0: Dummy 1
[ 20.510601] #1: Loopback 1
[ 20.511133] #2: MTPAV on parallel port at 0x378
[ 20.512642] VFS: Cannot open root device "ram0" or unknown-block(0,0): error -6
[ 20.514315] Please append a correct "root=" boot option; here are the available partitions:
[ 20.515530] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 20.516725] CPU: 0 PID: 1 Comm: swapper Not tainted 5.9.0-rc3-00224-g7b81ce7cdcef3 #1
[ 20.517887] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
[ 20.519091] Call Trace:
[ 20.519591] show_stack+0x62/0x68
[ 20.520156] dump_stack+0x20/0x22
[ 20.520720] panic+0x22f/0x4f7
[ 20.521264] ? printk+0x48/0x4a
[ 20.521814] ? preempt_count_sub+0x147/0x1c4
[ 20.522455] mount_block_root+0x3a3/0x3b2
[ 20.523070] mount_root+0x7a/0x7d
[ 20.523632] prepare_namespace+0x199/0x1ca
[ 20.524252] kernel_init_freeable+0x2a0/0x2b8
[ 20.524893] ? rest_init+0x115/0x115
[ 20.525475] kernel_init+0xf/0x188
[ 20.526049] ? rest_init+0x115/0x115
[ 20.526634] ret_from_fork+0x22/0x30
[ 20.527229] Kernel Offset: disabled
To reproduce:
# build kernel
cd linux
cp config-5.9.0-rc3-00224-g7b81ce7cdcef3 .config
make HOSTCC=gcc-9 CC=gcc-9 ARCH=x86_64 olddefconfig prepare modules_prepare bzImage
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email
Thanks,
Rong Chen
5 months, 3 weeks
[smsc95xx] 05b35e7eb9: WARNING:possible_circular_locking_dependency_detected
by kernel test robot
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: 05b35e7eb9a11bbe8102836965e634c04e712c88 ("smsc95xx: add phylib support")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: trinity
version:
with following parameters:
runtime: 300s
test-description: Trinity is a linux system call fuzz tester.
test-url: http://codemonkey.org.uk/projects/trinity/
on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 8G
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
+-------------------------------------------------------+------------+------------+
| | ad90a73f02 | 05b35e7eb9 |
+-------------------------------------------------------+------------+------------+
| boot_successes | 323 | 248 |
| boot_failures | 6 | 80 |
| INFO:rcu_preempt_self-detected_stall_on_CPU | 5 | 3 |
| RIP:iov_iter_copy_from_user_atomic | 4 | 3 |
| BUG:soft_lockup-CPU##stuck_for#s![trinity-c4:#] | 2 | 2 |
| Kernel_panic-not_syncing:softlockup:hung_tasks | 3 | 2 |
| BUG:soft_lockup-CPU##stuck_for#s![trinity-c6:#] | 1 | |
| RIP:__task_pid_nr_ns | 1 | |
| RIP:syscall_enter_from_user_mode | 1 | |
| WARNING:at_net/sched/sch_generic.c:#dev_watchdog | 1 | |
| RIP:dev_watchdog | 1 | |
| BUG:kernel_hang_in_test_stage | 1 | 3 |
| WARNING:possible_circular_locking_dependency_detected | 0 | 69 |
| WARNING:possible_recursive_locking_detected | 0 | 6 |
| invoked_oom-killer:gfp_mask=0x | 0 | 1 |
| Mem-Info | 0 | 1 |
+-------------------------------------------------------+------------+------------+
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <rong.a.chen(a)intel.com>
[ 276.006545] WARNING: possible circular locking dependency detected
[ 276.010112] 5.9.0-rc1-00605-g05b35e7eb9a11 #1 Not tainted
[ 276.013664] ------------------------------------------------------
[ 276.016801] trinity-c1/4424 is trying to acquire lock:
[ 276.020005] ffffffffa23705c8 (kexec_mutex){+.+.}-{3:3}, at: crash_get_memory_size+0x15/0x60
[ 276.023659]
[ 276.023659] but task is already holding lock:
[ 276.029215] ffff9a3cf9960c88 (&of->mutex){+.+.}-{3:3}, at: kernfs_seq_start+0x25/0xa0
[ 276.031572]
[ 276.031572] which lock already depends on the new lock.
[ 276.031572]
[ 276.039983]
[ 276.039983] the existing dependency chain (in reverse order) is:
[ 276.045899]
[ 276.045899] -> #2 (&of->mutex){+.+.}-{3:3}:
[ 276.051336] __lock_acquire+0x51c/0xb20
[ 276.054352] lock_acquire+0xab/0x3a0
[ 276.057203] __mutex_lock+0xac/0x9e0
[ 276.059937] kernfs_seq_start+0x25/0xa0
[ 276.062741] seq_read+0x93/0x420
[ 276.065388] vfs_read+0xb1/0x1c0
[ 276.067961] ksys_read+0x68/0xe0
[ 276.070463] do_syscall_64+0x33/0x40
[ 276.073039] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 276.075646]
[ 276.075646] -> #1 (&p->lock){+.+.}-{3:3}:
[ 276.080124] __lock_acquire+0x51c/0xb20
[ 276.082648] lock_acquire+0xab/0x3a0
[ 276.084973] __mutex_lock+0xac/0x9e0
[ 276.087252] seq_read+0x34/0x420
[ 276.089450] __kernel_read+0x71/0x180
[ 276.091647] kernel_read_file+0xd8/0x1a0
[ 276.093892] kernel_read_file_from_fd+0x44/0x80
[ 276.096103] kimage_file_alloc_init+0x86/0x240
[ 276.098313] __x64_sys_kexec_file_load+0x140/0x2a0
[ 276.100466] do_syscall_64+0x33/0x40
[ 276.102319] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 276.104485]
[ 276.104485] -> #0 (kexec_mutex){+.+.}-{3:3}:
[ 276.107942] check_prev_add+0x8e/0xa00
[ 276.109822] validate_chain+0x79b/0x1080
[ 276.111656] __lock_acquire+0x51c/0xb20
[ 276.113370] lock_acquire+0xab/0x3a0
[ 276.115071] __mutex_lock+0xac/0x9e0
[ 276.116726] crash_get_memory_size+0x15/0x60
[ 276.118445] kexec_crash_size_show+0xe/0x40
[ 276.120138] sysfs_kf_seq_show+0xb7/0x100
[ 276.121756] seq_read+0xba/0x420
[ 276.123289] do_iter_read+0x14e/0x1e0
[ 276.124831] compat_readv+0x9d/0xe0
[ 276.128646] do_compat_readv+0x58/0xc0
[ 276.130196] do_int80_syscall_32+0x41/0x60
[ 276.131494] entry_INT80_compat+0x88/0x8d
[ 276.132927]
[ 276.132927] other info that might help us debug this:
[ 276.132927]
[ 276.136642] Chain exists of:
[ 276.136642] kexec_mutex --> &p->lock --> &of->mutex
[ 276.136642]
[ 276.140393] Possible unsafe locking scenario:
[ 276.140393]
[ 276.142973] CPU0 CPU1
[ 276.144424] ---- ----
[ 276.145923] lock(&of->mutex);
[ 276.147223] lock(&p->lock);
[ 276.148759] lock(&of->mutex);
[ 276.150394] lock(kexec_mutex);
[ 276.151678]
[ 276.151678] *** DEADLOCK ***
[ 276.151678]
[ 276.154961] 4 locks held by trinity-c1/4424:
[ 276.156343] #0: ffff9a3ca6a0b0f0 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x4a/0x60
[ 276.158210] #1: ffff9a3cfa3f86f8 (&p->lock){+.+.}-{3:3}, at: seq_read+0x34/0x420
[ 276.159807] #2: ffff9a3cf9960c88 (&of->mutex){+.+.}-{3:3}, at: kernfs_seq_start+0x25/0xa0
[ 276.161779] #3: ffff9a3d37d85740 (kn->active#99){.+.+}-{0:0}, at: kernfs_seq_start+0x2d/0xa0
[ 276.163899]
[ 276.163899] stack backtrace:
[ 276.166312] CPU: 1 PID: 4424 Comm: trinity-c1 Not tainted 5.9.0-rc1-00605-g05b35e7eb9a11 #1
[ 276.168453] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
[ 276.170587] Call Trace:
[ 276.171886] dump_stack+0x96/0xe0
[ 276.173365] check_noncircular+0x162/0x180
[ 276.174963] ? stack_trace_save+0x4b/0x80
[ 276.176490] check_prev_add+0x8e/0xa00
[ 276.178029] validate_chain+0x79b/0x1080
[ 276.179573] __lock_acquire+0x51c/0xb20
[ 276.181059] lock_acquire+0xab/0x3a0
[ 276.182555] ? crash_get_memory_size+0x15/0x60
[ 276.184090] __mutex_lock+0xac/0x9e0
[ 276.185587] ? crash_get_memory_size+0x15/0x60
[ 276.187217] ? crash_get_memory_size+0x15/0x60
[ 276.188797] ? kernfs_seq_start+0x2d/0xa0
[ 276.190362] ? crash_get_memory_size+0x15/0x60
[ 276.191946] crash_get_memory_size+0x15/0x60
[ 276.193595] kexec_crash_size_show+0xe/0x40
[ 276.195155] sysfs_kf_seq_show+0xb7/0x100
[ 276.196666] seq_read+0xba/0x420
[ 276.198166] do_iter_read+0x14e/0x1e0
[ 276.199639] compat_readv+0x9d/0xe0
[ 276.201064] ? __fdget_pos+0x4a/0x60
[ 276.202634] ? lock_acquire+0xab/0x3a0
To reproduce:
# build kernel
cd linux
cp config-5.9.0-rc1-00605-g05b35e7eb9a11 .config
make HOSTCC=gcc-9 CC=gcc-9 ARCH=x86_64 olddefconfig prepare modules_prepare bzImage
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email
Thanks,
Rong Chen
5 months, 3 weeks
