linux-kernel - Re: 2.6.24 panics initializing ne2k in mips.

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 for Android: free password hash cracker in your pocket

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

Message-Id: <200801282351.01776.rob@landley.net>
Date:	Mon, 28 Jan 2008 23:51:00 -0600
From:	Rob Landley <rob@...dley.net>
To:	linux-kernel@...r.kernel.org
Cc:	linux-mips@...r.kernel.org, Ralf Baechle <ralf@...ux-mips.org>,
	Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: 2.6.24 panics initializing ne2k in mips.

On Monday 28 January 2008 02:17:37 Rob Landley wrote:
> The 2.6.23 kernel built for mips with the attached .config works fine for
> me under qemu (both big endian and little endian), but a 2.6.24 mips kernel
> segfaults initializing the ne2k driver (again when run under qemu).
>
> I've traced it to this commit:
>
>   http://kernel.org/hg/linux-2.6/rev/74258
>
> Version 74257 works, 74258 does not.

For the git users in the audience, that's commit 
30e748a507919a41f9eb4d10b4954f453325a37d

I just confirmed that:

A) today's -git still exhibits this bug.

B) Backing out the above irq-twiddling patch makes it stop exhibiting the bug 
for me.  (Boots to a shell prompt, it can use the network, etc.)

So that patch is definitely the trigger for the panic, and reverting the patch 
is one way to fix it.  (And probably the best way to make it work for 
2.6.24.1.)

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/