linux-kernel - Re: [PATCH update] firewire: reread config ROM when device reset the bus

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

Message-ID: <47CF4801.80307@s5r6.in-berlin.de>
Date:	Thu, 06 Mar 2008 02:25:21 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Jarod Wilson <jwilson@...hat.com>
CC:	linux1394-devel@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org,
	Kristian Høgsberg <krh@...planet.net>
Subject: Re: [PATCH update] firewire: reread config ROM when device reset
 the bus

I wrote:
> I wrote:
>> When I power the PC down there are lots of messages scrolling by
>> which look somewhat like lockdep spew.  I can't reproduce this merely by
>> module unloading though.  So don't put this patch into production yet.
> 
> /...a few hundreds reboots later.../
> 
> No, it is not this patch.  It is something else.  And whatever it is, it 
> is already present in 2.6.25-rc3.
> 
> To reproduce it, I need to plug an SBP-2 device in and out, then shut 
> the machine down (e.g. shutdown -h now, whereas shutdown -r now does not 
> seem to trigger the bug).
...
> I am now gradually removing debug options from the kernel to see which 
> debug facility is making the fuzz...

It is CONFIG_PROVE_LOCKING (Lock debugging: prove locking correctness).

At the moment when the machine powers itself off.

What a waste of time.
-- 
Stefan Richter
-=====-==--- --== --==-
http://arcgraph.de/sr/
--
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/