From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BE095FA3728 for ; Wed, 16 Oct 2019 15:24:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9B6F321848 for ; Wed, 16 Oct 2019 15:24:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389696AbfJPPYC (ORCPT ); Wed, 16 Oct 2019 11:24:02 -0400 Received: from smtprelay0139.hostedemail.com ([216.40.44.139]:50396 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2389061AbfJPPYC (ORCPT ); Wed, 16 Oct 2019 11:24:02 -0400 Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay08.hostedemail.com (Postfix) with ESMTP id 5FF50182CF408; Wed, 16 Oct 2019 15:24:00 +0000 (UTC) X-Session-Marker: 6A6F6540706572636865732E636F6D X-HE-Tag: paste39_3fc0e2c85714f X-Filterd-Recvd-Size: 2548 Received: from XPS-9350.home (unknown [47.151.152.152]) (Authenticated sender: joe@perches.com) by omf18.hostedemail.com (Postfix) with ESMTPA; Wed, 16 Oct 2019 15:23:57 +0000 (UTC) Message-ID: Subject: Re: [PATCH v3] x86, efi: never relocate kernel below lowest acceptable address From: Joe Perches To: Jarkko Sakkinen , Borislav Petkov Cc: Kairui Song , linux-kernel@vger.kernel.org, Ard Biesheuvel , Thomas Gleixner , Ingo Molnar , Matthew Garrett , Baoquan He , Dave Young , x86@kernel.org, linux-efi@vger.kernel.org, linux-integrity@vger.kernel.org Date: Wed, 16 Oct 2019 08:23:56 -0700 In-Reply-To: <20191016152014.GC4261@linux.intel.com> References: <20191012034421.25027-1-kasong@redhat.com> <20191014101419.GA4715@zn.tnic> <20191014202111.GP15552@linux.intel.com> <20191014211825.GJ4715@zn.tnic> <20191016152014.GC4261@linux.intel.com> Content-Type: text/plain; charset="ISO-8859-1" User-Agent: Evolution 3.32.1-2 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-integrity-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-integrity@vger.kernel.org On Wed, 2019-10-16 at 18:20 +0300, Jarkko Sakkinen wrote: > On Mon, Oct 14, 2019 at 11:18:25PM +0200, Borislav Petkov wrote: > > On Mon, Oct 14, 2019 at 11:21:11PM +0300, Jarkko Sakkinen wrote: > > > Was there a section in the patch submission documentation to point out > > > when people send patches with all the possible twists for an acronym? > > > > I don't think so. > > > > > This is giving me constantly gray hairs with TPM patches. > > > > Well, I'm slowly getting tired of repeating the same crap over and over > > again about how important it is to document one's changes and to write > > good commit messages. The most repeated answers I'm simply putting into > > canned reply templates because, well, saying it once or twice is not > > enough anymore. :-\ > > > > And yeah, I see your pain. Same here, actually. > > > > In the acronym case, I'd probably add a regex to my patch massaging > > script and convert those typos automatically and be done with it. > > Wonder if checkpatch.pl could be extended to know acronyms e.g. have a > db of known acronyms. ? examples please. checkpatch has a db for misspellings, I supposed another for acronyms could be added, but how would false positives be avoided?