linux-kernel - Re: [PATCH] firewire: core: check for 1394a compliant IRM, fix inaccessibility of Sony camcorder

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: <hu6p68$ft0$1@dough.gmane.org>
Date:	Wed, 02 Jun 2010 19:23:51 -0400
From:	"H.S." <hs.samix@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	linux1394-devel@...ts.sourceforge.net
Subject: Re: [PATCH] firewire: core: check for 1394a compliant IRM, fix inaccessibility
 of Sony camcorder

On 02/06/10 02:26 PM, Stefan Richter wrote:
> 
> I committed the patch to linux1394-2.6.git now, exposed it in the
> linux-next branch, and will send a pull request sometime next week.
> 
> I marked the commit to be back-merged into the stable kernel branches
> (2.6.32.y and newer).  Distributors will pick it up from there at their
> leisure, or earlier if they get a distro bug report that points them to
> the commit.
> 
> Thanks for testing the patched kernel.

Great! I am glad I was able to help.

> 
> I suppose either the local node became root node (node with highest node
> ID) and thus the camcorder stopped doing bus management things, or the
> camcorder chose the optimum gap count 5 for some reason and thus the
> Linux node saw no reason to do its bus management routine.  If you are
> very curious, you can look at node IDs and gap counts and more with the
> FireWire inspection utility gscanbus.


Okay. Thanks again for the explanations.

Warm regards.

-- 

Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.

--
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/