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]
Date:	Sat, 24 Jul 2010 10:01:28 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Martin Mokrejs <mmokrejs@...osome.natur.cuni.cz>
CC:	Jay Fenlason <fenlason@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	linux1394-devel@...ts.sourceforge.net
Subject: Re: 2.6.35-rc6 to 2.6.32.16: JuJu firewire issues

Stefan Richter wrote:
> Martin Mokrejs wrote at LKML:
>> Hi Jay,
>> Jay Fenlason wrote:
>>> On Fri, Jul 23, 2010 at 04:09:21PM +0200, Martin Mokrejs wrote:
>>>> Hi,
>>>>   I bought a external harddrive with firewire and USB interfaces (IcyBOX IB-250StUE-B).
>>>> If I connect it to a desktop computer A I get kernel crash during boot (see
>>>> both attached dmesg-*.txt files).
> 
> The crash which you reported is in sbp2 (of the old ieee1394 stack alias
> linux1394, not in firewire-sbp2 (of the new firewire stack alias juju).

I have logged your report as
	https://bugzilla.kernel.org/show_bug.cgi?id=16452
	nodemgr, sbp2: NULL pointer dereference in sbp2_update
but set its status to WILL_NOT_FIX for now.

The bug seems to be in the nodemgr component of the ieee1394 core
driver.  This is one of the things that were rewritten from scratch in
firewire-core with a fundamentally different implementation, for good
reasons.

Perhaps somebody else wants to look into a possible fix for this bug,
but this seems very unlikely.  (Basically, a bug fix already exists in
the form of firewire-core.)
-- 
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ