linux-kernel - [mm, oom_adj] 9954f89181: INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 31 May 2016 04:03:35 +0800
From:	kernel test robot <xiaolong.ye@...el.com>
To:	Michal Hocko <mhocko@...e.com>
Cc:	lkp@...org, LKML <linux-kernel@...r.kernel.org>,
	0day robot <fengguang.wu@...el.com>
Subject: [mm, oom_adj] 9954f89181: INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe
 lock order detected ]



FYI, we noticed the following commit:

https://github.com/0day-ci/linux Michal-Hocko/Handle-oom-bypass-more-gracefully/20160530-210927
commit 9954f891814d3f23e10036d2b6404cc80aaa461b ("mm, oom_adj: make sure processes sharing mm have same view of oom_score_adj")


on test machine: vm-kbuild-1G: 2 threads qemu-system-x86_64 -enable-kvm -cpu Haswell,+smep,+smap with 1G memory

caused below changes:


+----------------+------------+------------+
|                | 04e2f60b36 | 9954f89181 |
+----------------+------------+------------+
| boot_successes | 8          | 4          |
+----------------+------------+------------+




======================================================
======================================================
[ INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ]
[ INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ]
4.7.0-rc1-next-20160530-00003-g9954f89 #288 Not tainted
4.7.0-rc1-next-20160530-00003-g9954f89 #288 Not tainted
------------------------------------------------------
------------------------------------------------------
(md-udevd)/256 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
(md-udevd)/256 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
 ( (&(&p->alloc_lock)->rlock&(&p->alloc_lock)->rlock){+.+...}){+.+...}, at: , at: [<ffffffff811d1008>] find_lock_task_mm+0x98/0x1b0
[<ffffffff811d1008>] find_lock_task_mm+0x98/0x1b0

and this task is already holding:

and this task is already holding:
 ( (&(&sighand->siglock)->rlock&(&sighand->siglock)->rlock){......}){......}, at: , at: [<ffffffff810c1e09>] __lock_task_sighand+0xd9/0x370
[<ffffffff810c1e09>] __lock_task_sighand+0xd9/0x370
which would create a new lock dependency:
which would create a new lock dependency:
 ( (&(&sighand->siglock)->rlock&(&sighand->siglock)->rlock){......}){......} -> -> ( (&(&p->alloc_lock)->rlock&(&p->alloc_lock)->rlock){+.+...}){+.+...}


FYI, raw QEMU command line is:

	qemu-system-x86_64 -enable-kvm -cpu Haswell,+smep,+smap -kernel /pkg/linux/x86_64-randconfig-i0-201622/gcc-6/9954f891814d3f23e10036d2b6404cc80aaa461b/vmlinuz-4.7.0-rc1-next-20160530-00003-g9954f89 -append 'root=/dev/ram0 user=lkp job=/lkp/scheduled/vm-kbuild-1G-11/bisect_boot-1-debian-x86_64-2015-02-07.cgz-x86_64-randconfig-i0-201622-9954f891814d3f23e10036d2b6404cc80aaa461b-20160531-56076-kodgfu-0.yaml ARCH=x86_64 kconfig=x86_64-randconfig-i0-201622 branch=linux-devel/devel-catchup-201605302311 commit=9954f891814d3f23e10036d2b6404cc80aaa461b BOOT_IMAGE=/pkg/linux/x86_64-randconfig-i0-201622/gcc-6/9954f891814d3f23e10036d2b6404cc80aaa461b/vmlinuz-4.7.0-rc1-next-20160530-00003-g9954f89 max_uptime=600 RESULT_ROOT=/result/boot/1/vm-kbuild-1G/debian-x86_64-2015-02-07.cgz/x86_64-randconfig-i0-201622/gcc-6/9954f891814d3f23e10036d2b6404cc80aaa461b/0 LKP_SERVER=inn earlyprintk=ttyS0,115200 systemd.log_level=err debug apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 prompt_ramdisk=0 console=ttyS0,115200 console=tty0 vga=normal rw ip=::::vm-kbuild-1G-11::dhcp'  -initrd /fs/sdf1/initrd-vm-kbuild-1G-11 -m 1024 -smp 2 -device e1000,netdev=net0 -netdev user,id=net0,hostfwd=tcp::23010-:22 -boot order=nc -no-reboot -watchdog i6300esb -rtc base=localtime -device virtio-scsi-pci,id=scsi0 -drive file=/fs/sdf1/disk0-vm-kbuild-1G-11,if=none,id=hd0,media=disk,aio=native,cache=none -device scsi-hd,bus=scsi0.0,drive=hd0,scsi-id=1,lun=0 -drive file=/fs/sdf1/disk1-vm-kbuild-1G-11,if=none,id=hd1,media=disk,aio=native,cache=none -device scsi-hd,bus=scsi0.0,drive=hd1,scsi-id=1,lun=1 -drive file=/fs/sdf1/disk2-vm-kbuild-1G-11,if=none,id=hd2,media=disk,aio=native,cache=none -device scsi-hd,bus=scsi0.0,drive=hd2,scsi-id=1,lun=2 -drive file=/fs/sdf1/disk3-vm-kbuild-1G-11,if=none,id=hd3,media=disk,aio=native,cache=none -device scsi-hd,bus=scsi0.0,drive=hd3,scsi-id=1,lun=3 -drive file=/fs/sdf1/disk4-vm-kbuild-1G-11,if=none,id=hd4,media=disk,aio=native,cache=none -device scsi-hd,bus=scsi0.0,drive=hd4,scsi-id=1,lun=4 -pidfile /dev/shm/kboot/pid-vm-kbuild-1G-11 -serial file:/dev/shm/kboot/serial-vm-kbuild-1G-11 -daemonize -display none -monitor null 





Thanks,
Kernel Test Robot

View attachment "config-4.7.0-rc1-next-20160530-00003-g9954f89" of type "text/plain" (99360 bytes)

Download attachment "dmesg.xz" of type "application/octet-stream" (19200 bytes)