linux-kernel - Re: e1000 crash on 3.15.0-rc4

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:	Sun, 11 May 2014 13:12:12 +0100
From:	Ben Hutchings <ben@...adent.org.uk>
To:	bo.li.liu@...cle.com
Cc:	e1000-devel@...ts.sourceforge.net, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: e1000 crash on 3.15.0-rc4

On Wed, 2014-05-07 at 13:32 +0800, Liu Bo wrote:
> Hi,
> 
> I'm using qemu to load kernel of 3.15.0-rc4, and with CONFIG_E1000=y,
> everying is ok, but with CONFIG_E1000=m, I got the following crash:
> 
> [...]
> [    6.020409] tsc: Refined TSC clocksource calibration: 2491.912 MHz
> [    6.074925] floppy: Unknown symbol mutex_lock (err 0)
> [    6.128579] virtio_blk: Unknown symbol mutex_lock (err 0)
> [    6.141264] i2c_core: Unknown symbol mutex_lock (err 0)

Really???

> [    6.167490] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
> [    6.168240] e1000: Copyright (c) 1999-2006 Intel Corporation.
> [    6.171078] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
> [    6.190295] BUG: spinlock bad magic on CPU#3, systemd-udevd/208
[...]

I think you may have rebuilt the kernel with lockdep enabled, but
haven't also rebuilt and installed the modules with lockdep enabled.

You should enable symbol versions to catch such mistakes.

Ben.

-- 
Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.

Download attachment "signature.asc" of type "application/pgp-signature" (829 bytes)