linux-kernel - Re: 2.6.25-mm1: kmmcd NULL pointer dereference at klist

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]

Message-Id: <200805122143.33748.rjw@sisk.pl>
Date:	Mon, 12 May 2008 21:43:33 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Pierre Ossman <drzeus-list@...eus.cx>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Andy Isaacson <adi@...apodia.org>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.25-mm1: kmmcd NULL pointer dereference at klist_del+0xe/0x30

On Monday, 12 of May 2008, Pierre Ossman wrote:
> On Fri, 9 May 2008 16:47:38 -0700
> Andrew Morton <akpm@...ux-foundation.org> wrote:
> 
> > On Fri, 9 May 2008 10:19:56 -0700
> > Andy Isaacson <adi@...apodia.org> wrote:
> > 
> > > Got this twice with 2.6.25-mm1 on my Thinkpad X40, AData 16GB SDHC card
> > > in mmc0 but no filesystem mounted.  I think the oops happened at
> > > suspend/resume time.  Previous kernel was 2.6.25-rc5-mm1 which didn't
> > > exhibit this problem across multiple suspend-resume cycles.
> > > 
> > > Complete logs and pretty much everything else you could want at
> > > http://web.hexapodia.org/~adi/bobble/bobble_2.6.25-mm1-dirty_20080509100634/
> > > 
> > > [104375.816331] BUG: unable to handle kernel NULL pointer dereference at 0000000c
> > > [104375.816338] IP: [<c02d86ce>] klist_del+0xe/0x30
> > 
> > This could be one of those nasty situations where one driver leaves a mess
> > behind it and then another driver later comes along and trips over that
> > mess.
> > 
> 
> There were some problems with removing devices during suspend (which
> the MMC layer does), but AFAIK those patches were backed out and were
> only supposed to come back in a form that allowed such usage. Rafael
> should have the most correct information on that subject.

Those changes went away for good.  At the moment, we only print a warning
if there's a suspend ordering violation.

The problem described here looks like the one fixed by commits
29591b92e19f409d5ad4c099c2b7b5ea56f50dfa and
08119e8966e993993d0ba92b2fba38c582c8f787,
so Andy, please try the current linux-next or even -rc2.

Thanks,
Rafael
--
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/