linux-kernel - Re: Issue with firewire from 2.6.35.9 to 2.6.36.1

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: <20101207150411.11bb5889@stein>
Date:	Tue, 7 Dec 2010 15:04:11 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Clemens Ladisch <clemens@...isch.de>
Cc:	linux-kernel@...r.kernel.org,
	linux1394-devel <linux1394-devel@...ts.sourceforge.net>,
	Robin Cook <rcook@...ms.net>,
	Maxim Levitsky <maximlevitsky@...il.com>
Subject: Re: Issue with firewire from 2.6.35.9 to 2.6.36.1

On Dec 07 Clemens Ladisch wrote:
> Stefan Richter wrote:
> > I wonder which of our options is preferable:
> >   - Change fw-ohci from MSI blacklisting to whitelisting.  Agere FW643
> >     rev 07 is the only chip that can be whitelisted.
> >   - Simply drop MSI support altogether.

Blacklisting is also still an option if we extend the table by a
revision field:
   match = ... && (ohci_quirks[i].revision == ANY_REVISION ||
                   dev->revision <= ohci_quirks[i].revision) && ...;
If we ever need an dev->revision >= ohci_quirks[i].revision match, the
"break after first match" rule can be put to use or more tricks be
added.

> That depends on whether the maintainer can afford the effort of
> maintaining the whitelist.

I heard the maintainer is an FW643-E owner.  Maybe he accepts the
maintenance burden for personal gain (less MMIO reads than with shared
IRQs).  He might get fed up when new 1394 controllers with working MSI
support start to appear on the market in a monthly rhythm or so.

Blacklist maintenance OTOH would be worse for all concerned, since
evidently not every MSI related bug is so easy to identify like with
JMB38x and VT6315.  Even such simple cases will become more problematic
as more time goes by since the 2.6.36 release.  Though with the current
rate of OHCI 1394 product releases, blacklisting seems not to be a big
deal either.
-- 
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/