Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933919Ab3CTBHc (ORCPT ); Tue, 19 Mar 2013 21:07:32 -0400 Received: from co1ehsobe003.messaging.microsoft.com ([216.32.180.186]:6738 "EHLO co1outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754430Ab3CTBH3 (ORCPT ); Tue, 19 Mar 2013 21:07:29 -0400 X-Forefront-Antispam-Report: CIP:157.56.236.101;KIP:(null);UIP:(null);IPV:NLI;H:BY2PRD0510HT004.namprd05.prod.outlook.com;RD:none;EFVD:NLI X-SpamScore: 3 X-BigFish: PS3(zzda00hzz1f42h1ee6h1de0h1202h1e76h1d1ah1d2ahzz8275bh179de6iz2fh2a8h668h839h93fhd24hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18deh18e1h1946h19b5h1ad9h1b0ah17ej1155h) From: Matthew Garrett To: "H. Peter Anvin" CC: "linux-kernel@vger.kernel.org" , "linux-security-module@vger.kernel.org" , "linux-efi@vger.kernel.org" , "kexec@lists.infradead.org" , "linux-pci@vger.kernel.org" Subject: Re: [PATCH 01/12] Security: Add CAP_COMPROMISE_KERNEL Thread-Topic: [PATCH 01/12] Security: Add CAP_COMPROMISE_KERNEL Thread-Index: Ac4lB0hhmvU0usyXI0yxxCAslUbX+Q== Date: Wed, 20 Mar 2013 01:07:25 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [::] Content-Type: text/plain; charset="utf-8" Content-ID: <772F9D422F826A4E91A028F471B9D3A7@nebula.com> MIME-Version: 1.0 X-OriginatorOrg: nebula.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id r2K17Xb9029648 Content-Length: 314 Lines: 3 Yeah, I'd like the option of relaxing restrictions when drivers explicitly opt in based on iommu support. -- Matthew Garrett | matthew.garrett@nebula.com????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?