linux-kernel - Re: [NTB] 26b3a37b92: WARNING:at_kernel/params.c:#param_sysfs

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-prev] [day] [month] [year] [list]

Date:   Fri, 26 Jul 2019 12:08:39 -0600
From:   Logan Gunthorpe <logang@...tatee.com>
To:     kernel test robot <lkp@...el.com>
Cc:     Jon Mason <jdmason@...zu.us>, Dave Jiang <dave.jiang@...el.com>,
        Allen Hubbe <allenbh@...il.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>, lkp@...org
Subject: Re: [NTB] 26b3a37b92: WARNING:at_kernel/params.c:#param_sysfs_init



On 2019-07-26 2:23 a.m., kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-4.9):
> 
> commit: 26b3a37b928457ba2cd98eaf6d7b0feca5a30fa6 ("NTB: Introduce MSI library")
> https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git master
> 
> in testcase: locktorture
> with following parameters:
> 
> 	runtime: 300s
> 	test: cpuhotplug
> 
> test-description: This torture test consists of creating a number of kernel threads which acquire the lock and hold it for specific amount of time, thus simulating different critical region behaviors.
> test-url: https://www.kernel.org/doc/Documentation/locking/locktorture.txt
> 
> 
> on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 2G
> 
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> 
> 
> +----------------------------------------------+------------+------------+
> |                                              | d217e07b32 | 26b3a37b92 |
> +----------------------------------------------+------------+------------+
> | boot_successes                               | 4          | 0          |
> | boot_failures                                | 0          | 4          |
> | WARNING:at_kernel/params.c:#param_sysfs_init | 0          | 4          |
> | RIP:param_sysfs_init                         | 0          | 4          |
> +----------------------------------------------+------------+------------+
> 

Oh shoot.

This confusing report is caused by me accidentally leaving the MODULE_
defines in a file that ended up not being a module. I'll send a patch ASAP.

Logan