linux-kernel - Re: BUG: Null pointer dereference (2.6.21-rc7)

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

Message-ID: <Pine.LNX.4.64.0704231633210.25153@server.thyself>
Date:	Mon, 23 Apr 2007 16:39:45 +0000 (GMT)
From:	William Heimbigner <icxcnika@....tar.cc>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	linux-kernel@...r.kernel.org, Peter Osterlund <petero2@...ia.com>
Subject: Re: BUG: Null pointer dereference (2.6.21-rc7)

On Mon, 23 Apr 2007, William Heimbigner wrote:
> On Mon, 23 Apr 2007, Andrew Morton wrote:
>>  It certainly is.  Are you able to identify an earlier kernel in which this
>>  didn't happen?  2.6.20?  An earlier 2.6.21-rcX?
>
> I'll try .18 and .20 and see where that gets me - this is my first time 
> trying to set up packet writing.

Ok, on 2.6.18, I still get the warning about a recursive lock, but no dump 
regarding a null pointer dereference. The command still fails, however, 
with pkt_get_last_written_failed. On 2.6.20, I get an error similar to the
one I orignally posted (first the recursive lock warning, seconds later,
null pointer dereference).

Not sure about the recursive lock, but something between .18 and .20 
happened such that the packet writing driver didn't fail gracefully.

On a side (offtopic) note, I noticed that ACPI support changed for the 
better in very recent kernels - on both .18 and .20, there were severe 
and early errors unless I specified acpi=off

I'll see if I can figure out exactly where from 2.6.18 to .20 things went 
wrong,
William Heimbigner
icxcnika@....tar.cc
-
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/