linux-kernel - Re: ohci1394 regression in 2.6.19-rc1

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: <45268FB1.6080605@s5r6.in-berlin.de>
Date:	Fri, 06 Oct 2006 19:17:37 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Alistair John Strachan <s0348365@....ed.ac.uk>
CC:	Linus Torvalds <torvalds@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	bcollins@...ian.org, linux1394-devel@...ts.sourceforge.net
Subject: Re: ohci1394 regression in 2.6.19-rc1

I wrote:
> I saw the messages and the delay that you described now too, using Linux
> 2.6.18 + all IEEE 1394 updates. I will continue to narrow the cause down.

It's as I suspected:
"ieee1394: nodemgr: switch to kthread api, replace reset semaphore"
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=d2f119fe319528da8c76a1107459d6f478cbf28c

Before that, I get a selfID-complete event, then nodemgr starts its
work. After that its the reverse, which lets nodemgr inject a packet
before the bus is completely ready. (So it's actually a regression in
ieee1394 core's high-level functions, not in ohci1394. And it's harmless.)

I will post when I have a fix.
-- 
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/