[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150506175541.GN5622@wotan.suse.de>
Date: Wed, 6 May 2015 19:55:41 +0200
From: "Luis R. Rodriguez" <mcgrof@...e.com>
To: "Luis R. Rodriguez" <mcgrof@...not-panic.com>
Cc: rusty@...tcorp.com.au, dhowells@...hat.com, ming.lei@...onical.com,
seth.forshee@...onical.com, kyle@...nel.org,
akpm@...ux-foundation.org, gregkh@...uxfoundation.org,
keescook@...omium.org, casey@...aufler-ca.com, tiwai@...e.de,
mjg59@...f.ucam.org, wireless-regdb@...ts.infradead.org,
linux-wireless@...r.kernel.org, jlee@...e.com,
linux-kernel@...r.kernel.org
Subject: Re: [RFC v1 00/12] kernel/firmware/wireless: firmware digital
signature checks
On Tue, May 05, 2015 at 05:44:18PM -0700, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@...e.com>
>
> * first set: [1-4] few fixes and core changes in order to consider digital
> firmware signature support. Please consider these for integration. Patch
> 2 generalizes module signing as system data signing and can very likely
> just be ignored unles the second set seems more reasonable to start
> considering. One of these goes as a stable fix.
Rusty, based on feedback only one patch is relevant for upstream consideration
then on your end:
1 - kernel/params.c: export param_ops_bool_enable_only
Ming, as for firmware_class, this patch should be reviewed and
considered for upstream consideration:
4 - firmware: fix possible use after free on name on asynchronous request
The patches are orthogonal to each other so they can be considered
separately, and can go in through separate trees.
Luis
--
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