Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp272294ybi; Fri, 24 May 2019 03:40:30 -0700 (PDT) X-Google-Smtp-Source: APXvYqzgxOT/aScJ+e4pUtUce5XNK2lv78ZlbtBdFQ0oiWUcom4UEpufwylGsolVujNJikubZa+3 X-Received: by 2002:a63:5c1b:: with SMTP id q27mr105667759pgb.127.1558694430539; Fri, 24 May 2019 03:40:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558694430; cv=none; d=google.com; s=arc-20160816; b=TmsZ9p3tHue0sJUwLUsJdfE3KCjqDb4c6Fs1r2fDUOYhftXNTNxCfPUWIl5ByBZLx/ JZaeT9JK1TSYjZ7++ArSntTUFpvznNq753F+S9TUrJ7baR+JVMurkEGaSZuemPYewiqo BfvmUBDbfQDJDnELauf8rz22zGldjpDYlgF9P6i3WPbqtBSfCkBTRNooEJw1Qh4L7UE8 W0h45sm08AmYXl8gcmKDBajAmLoOg+zjtnfCwGZZKv4jdWflVY6appqcyTlIVzSCxGQp xX5KcJwGNTlMYARHHGTnVQ9ePzct1WTpi5gbQEyLXJc30j1N/z3BcPl/PtyFp6lkWtw2 /BRA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:organization:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=rysuXhEKs7Pe3X8cjkUO0wnF7D3e8K4PIa/Nd5Rabm4=; b=eL3Z5A8srMnRjRvAgEkfrk2ZrVKEwLopDY6xu6aANDAlG0VSoku9mHRogkQqANaZI0 yGsq36BhTwCUmqnwJgwr2mUXJS+Q3s2W0tX+kobi8Q9mF4UOX95B4Ix5NU/6FIf+11bF KT55jINPFfuXKUAchRmzsgYhjtbwuG/gE96EhQQNZO9e2gVZCwJUl439IDldXGmf0/A0 RnZrt8OI7RGXchEN8XK9LgTCsgfdp68O4exhsCIhslgWd6BqucaCiEzDqcKaUyIfgNa+ MaG/sQ5Qu+Iu/WRPxgci3UX6Xai0SJxEQmd4Sq2Jlaq354H+HS9/8XW+Oqc6qDQCKEDC tTQQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id gn11si3394891plb.119.2019.05.24.03.40.15; Fri, 24 May 2019 03:40:30 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390242AbfEXKiv (ORCPT + 99 others); Fri, 24 May 2019 06:38:51 -0400 Received: from mga02.intel.com ([134.134.136.20]:37305 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390248AbfEXKiv (ORCPT ); Fri, 24 May 2019 06:38:51 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 May 2019 03:38:50 -0700 X-ExtLoop1: 1 Received: from jsakkine-mobl1.tm.intel.com (HELO localhost) ([10.237.50.189]) by orsmga005.jf.intel.com with ESMTP; 24 May 2019 03:38:46 -0700 Date: Fri, 24 May 2019 13:38:46 +0300 From: Jarkko Sakkinen To: James Morris Cc: Matthew Garrett , linux-integrity@vger.kernel.org, peterhuewe@gmx.de, jgg@ziepe.ca, roberto.sassu@huawei.com, linux-efi@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, tweek@google.com, bsz@semihalf.com Subject: Re: [PATCH V7 0/4] Add support for crypto agile logs Message-ID: <20190524103846.GA11695@linux.intel.com> References: <20190520205501.177637-1-matthewgarrett@google.com> <20190523121449.GA9997@linux.intel.com> <20190523122610.GA12327@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 24, 2019 at 02:54:20AM +1000, James Morris wrote: > On Thu, 23 May 2019, Jarkko Sakkinen wrote: > > > On Thu, May 23, 2019 at 03:14:49PM +0300, Jarkko Sakkinen wrote: > > > On Mon, May 20, 2019 at 01:54:57PM -0700, Matthew Garrett wrote: > > > > Identical to previous version except without the KSAN workaround - Ard > > > > has a better solution for that. > > > > > > > > > Reviewed-by: Jarkko Sakkinen > > > Tested-by: Jarkko Sakkinen > > > > Only applied to my master at this point becaues the patches from > > my earlier PRs are not yet mirrored to security/next-general. > > Which PRs are these? > > btw, Linus wants security subsystem maintainers to submit PRs directly to > him from now on. > > I'll only be carrying patches for the core LSM and new security mechanisms > before they're merged and have a maintainer assigned. I'm referring to these: https://lore.kernel.org/linux-integrity/20190329115544.GA27351@linux.intel.com/ I got response from you that those were applied and there is another response in that thread that they are being sent to Linus. That is why I haven't done anything since. Most of them are critical fixes to v5.1 changes. Should I now take the action to send a PR to Linus and tag them to stable? /Jarkko