linux-kernel - Re: Where to report firmware bugs

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: <1259053454.29729.272.camel@macbook.infradead.org>
Date:	Tue, 24 Nov 2009 09:04:14 +0000
From:	David Woodhouse <dwmw2@...radead.org>
To:	"Luis R. Rodriguez" <mcgrof@...il.com>
Cc:	linux-kernel@...r.kernel.org,
	Marcel Holtmann <marcel@...tmann.org>,
	"John W. Linville" <linville@...driver.com>,
	Samir Gadkari <Samir.Gadkari@...eros.com>,
	Vikram Kandukuri <Vikram.Kandukuri@...eros.com>
Subject: Re: Where to report firmware bugs

On Mon, 2009-11-23 at 09:41 -0800, Luis R. Rodriguez wrote:
> We now have open firmware for at least one wireless device upstream,
> the ar9170 device firmware [1]. Granted no specific point releases
> have been made yet but it should be possible in the future to do so.
> I'd also like to see more open firmware in the future. I also just
> reviewed some simple driver for our bluetooth devices, the ath3k
> driver and it seems clear to me in these cases that firmware will do
> everything and chances are the actual driver won't have much bugs.
> 
> So -- for the cases of open firmware, or in cases where we have
> firmware where it does most of the job of supporting the device where
> should we send users to report bugs to? The kernel bugzilla at least
> does not seem to have a section for firmware? Should it?
> 
> In the case of iwl3945 it seems users report bugs directly on the
> kernel.org and refer the driver directly, we'll follow that for now,
> but for cases where the firmware *is* the issue it would seem easier
> to be able to search for issues specifically for firmware.

Well, Intel wireless also has its own bugzilla. Although perhaps it's
quite a bad example because the firmware bugs are just too opaque and
don't seem to get fixed. Bug #2037 is an example. It would benefit from
opening up the firmware too, so that we can actually debug and fix it.

I'm not entirely sure it's a good idea to use kernel.org bugzilla for
firmware bugs. Each firmware is its own individual project, and should
have its own bug tracking system.

On the other hand, it doesn't cost us much to add a firmware section to
bugzilla, and it reduces the amount of infrastructure that people need
to provide when they open up their firmware -- so maybe it make sense.
We want to encourage people to open up as much as possible, after all.

-- 
dwmw2

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