linux-kernel - Re: Firewire lockup on 2.6.22.3 in SMP but not UP, old drivers

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: <46CDEBB4.4020001@s5r6.in-berlin.de>
Date:	Thu, 23 Aug 2007 22:19:00 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Andrew Burgess <aab@...hlid.com>
CC:	linux1394-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: Firewire lockup on 2.6.22.3 in SMP but not UP, old drivers

Andrew Burgess wrote:
> what's the best way to proceed? Debug old drivers or
> switch to new ones?

As I mentioned in the branch of the discussion which lost the Cc: LKML,
this kind of bug looks like requiring a good look at the interaction of
raw1394's and ohci1394's locking (and maybe ieee1394's, but this seems
less likely).

It's hard work, and I don't have much experience with the code in
question nor do I have much time at the moment nor is there anybody else
who fixes ieee1394 subsystem bugs on a regular basis.  Nevertheless,
this kind of bugs should still be fixed in the "old" drivers.  They
haven't reached their end of life yet.
-- 
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/