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=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham 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 5B4E2C3279B for ; Sun, 8 Jul 2018 13:25:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 19E9920882 for ; Sun, 8 Jul 2018 13:25:29 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 19E9920882 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linuxfoundation.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754346AbeGHNZY (ORCPT ); Sun, 8 Jul 2018 09:25:24 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:44530 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754168AbeGHNZW (ORCPT ); Sun, 8 Jul 2018 09:25:22 -0400 Received: from localhost (unknown [46.44.180.42]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id 6E1D8C8A; Sun, 8 Jul 2018 13:25:21 +0000 (UTC) Date: Sun, 8 Jul 2018 15:25:19 +0200 From: Greg Kroah-Hartman To: Michael Ellerman Cc: Ingo Molnar , Vlastimil Babka , linux-kernel@vger.kernel.org, stable@vger.kernel.org, Dave Hansen , Linus Torvalds , Peter Zijlstra , Thomas Gleixner , akpm@linux-foundation.org, dave.hansen@intel.com, linux-mm@kvack.org, linuxram@us.ibm.com, shakeelb@google.com, shuah@kernel.org, Sasha Levin Subject: Re: [PATCH 4.16 234/279] x86/pkeys/selftests: Adjust the self-test to fresh distros that export the pkeys ABI Message-ID: <20180708132519.GA29528@kroah.com> References: <20180618080608.851973560@linuxfoundation.org> <20180618080618.495174114@linuxfoundation.org> <20180703114241.GA19730@kroah.com> <877emakynf.fsf@concordia.ellerman.id.au> <20180705071937.GA2636@gmail.com> <87va9qj9tq.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87va9qj9tq.fsf@concordia.ellerman.id.au> User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jul 08, 2018 at 08:33:37PM +1000, Michael Ellerman wrote: > Ingo Molnar writes: > > * Michael Ellerman wrote: > >> Greg Kroah-Hartman writes: > >> > On Tue, Jul 03, 2018 at 01:36:43PM +0200, Vlastimil Babka wrote: > >> >> On 06/18/2018 10:13 AM, Greg Kroah-Hartman wrote: > >> >> > 4.16-stable review patch. If anyone has any objections, please let me know. > >> >> > >> >> So I was wondering, why backport such a considerable number of > >> >> *selftests* to stable, given the stable policy? Surely selftests don't > >> >> affect the kernel itself breaking for users? > >> > > >> > These came in as part of Sasha's "backport fixes" tool. It can't hurt > >> > to add selftest fixes/updates to stable kernels, as for some people, > >> > they only run the selftests for the specific kernel they are building. > >> > While others run selftests for the latest kernel on older kernels, both > >> > of which are valid ways of testing. > >> > >> I don't have a problem with these sort of patches being backported, but > >> it seems like Documentation/process/stable-kernel-rules.txt could use an > >> update? > >> > >> I honestly don't know what the rules are anymore. > > > > Self-tests are standalone tooling which help the testing of the kernel, and it > > makes sense to either update all of them, or none of them. > > Yes I know what selftests are. > > > Here it makes sense to update all of them, because if a self-test on a stable > > kernel shows a failure then a fix is probably missing from -stable, right? > > Usually, though it's not always that simple IME. > > But sure, I don't have a problem with updating selftests, I said that before. > > > Also note that self-test tooling *cannot possibly break the kernel*, because they > > are not used in the kernel build process, so the normally conservative backporting > > rules do not apply. > > Right. So stable-kernel-rules.txt could use an update to mention that. > > > My comment was less about this actual patch and more about the new > reality of patches being backported to stable based on Sasha's tooling, > which seems to be much more liberal than anything we've done previously. > > I don't generally have any objection to that process, though it possibly > could have been more widely announced. But, it would be good if > stable-kernel-rules.txt was updated to mention it. > > I've had several people ask me "hey my patch got backported to stable > but I didn't ask for it - is that OK, what's going on?" etc. Why didn't those people just ask us? To not do so is very strange, it's not like we are hard to find :) > I guess I should just send a patch to update it, but I don't really know > what it should say. I don't think it really needs any changes, as the selftests is just a corner case that is easily explained if anyone cares enough to actually ask :) thanks, greg k-h