Received: by 10.192.165.148 with SMTP id m20csp1923210imm; Thu, 3 May 2018 07:34:02 -0700 (PDT) X-Google-Smtp-Source: AB8JxZrHtHxA72k/Ttdy416KYATFE4RdDTEU+L6BBW/Nxt09UUAj3EmAu0oNV6Ekam2yp7xq+qQ7 X-Received: by 2002:a63:6242:: with SMTP id w63-v6mr19112295pgb.377.1525358042129; Thu, 03 May 2018 07:34:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525358042; cv=none; d=google.com; s=arc-20160816; b=TBfoaQ+T36lMwJJvw2LS1mlATHXalQl0v0lOYrpo3nxhNtJlQWEcYUdR34VQmoBdHR zW8vwtsIRmfMd/TRXhXtMzXYZA18gPcHDhkYSGv0k+rZrlyN+WHlExQngDAaIcEeurF0 +2BntAV6JJHgkW8GLFZQzfS9hdo/ZEuASDyikHIG+J+lILcwI+ISSdGwMphaxghXZF+2 YKKdHzdVUSm/brtYLcZl0UsFnlFVW1amMccBrPaUnfiC3KQEufCMPX/lxWqnv3AM766z JRf7Uc9ilbF4y71euccmEEXowje9lEqgkqmUcYyAMLkRtnANBzUIBvNSSoqQ57R8JUZ6 uVmA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :dkim-signature:arc-authentication-results; bh=dqAGPCB3ATU88t3Bn0HtVNJ4xYs0ka38R/HKJAxsNnc=; b=XWQ/iR2dWA5veEORWQaoVGo5RkOstAFuiVcmZehMdOFG6KXMnpuY/fYpBgcE9gkWVZ pDlHQAbMFFpdDNHsXMvqgHVIGHL72rRczByDpBUckS5K/7awcXgFGHJjJQIdfYhxffed 525iwARtFPWMk0Mzhn8aGpguNFbG6/ZCM23NwCR5jDk3Ae4SmMEge3L6QDrwW22CbIX9 Q6Mati5KVJj6986BtRMkrZsz0I/F1WaA7GJjFv49YrPd15dHw/tn7a1dU8KqrMuLdMkE XhzkRixIheu3bAWcEHksTrcECXZGlT6MGgFE0FVtrg7hS1VHVs02ek+c7n/lbcGfulzj 1LLQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@hansenpartnership.com header.s=20151216 header.b=UhAWc7Ag; 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=hansenpartnership.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p11-v6si4807517pgn.267.2018.05.03.07.33.48; Thu, 03 May 2018 07:34:02 -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; dkim=fail header.i=@hansenpartnership.com header.s=20151216 header.b=UhAWc7Ag; 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=hansenpartnership.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751399AbeECOdL (ORCPT + 99 others); Thu, 3 May 2018 10:33:11 -0400 Received: from bedivere.hansenpartnership.com ([66.63.167.143]:58562 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751027AbeECOdH (ORCPT ); Thu, 3 May 2018 10:33:07 -0400 Received: from localhost (localhost [127.0.0.1]) by bedivere.hansenpartnership.com (Postfix) with ESMTP id 418348EE28A; Thu, 3 May 2018 07:33:06 -0700 (PDT) Received: from bedivere.hansenpartnership.com ([127.0.0.1]) by localhost (bedivere.hansenpartnership.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BE1cj3agvQGG; Thu, 3 May 2018 07:33:06 -0700 (PDT) Received: from [153.66.254.194] (unknown [50.35.65.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by bedivere.hansenpartnership.com (Postfix) with ESMTPSA id A2D148EE092; Thu, 3 May 2018 07:33:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=hansenpartnership.com; s=20151216; t=1525357986; bh=9L3I4rEdMLz+ZLrXNI8LdVKjkHJMZ7mjQPRBWmUWDiY=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=UhAWc7AgcCOhDcuM2A4kLdSJNWyw6C3VK8ynjIH1GnhbXiFWvwA93FFJtHUSHMElN p+1g6rpVIZCgz4uSZ/X8x7UluLBmwgLpox8uCLLJRFIUfP2UIxNnyStqOulWjjsov3 s4VybMYgMUfDeVUFga2zLiVu0tCGx6J+u8o8SjsU= Message-ID: <1525357984.3225.12.camel@HansenPartnership.com> Subject: Re: [Ksummit-discuss] bug-introducing patches From: James Bottomley To: Jani Nikula , "Theodore Y. Ts'o" , Sasha Levin Cc: Greg KH , "linux-kernel@vger.kernel.org" , "ksummit-discuss@lists.linuxfoundation.org" , "w@1wt.eu" Date: Thu, 03 May 2018 07:33:04 -0700 In-Reply-To: <877eol808s.fsf@intel.com> References: <20180501163818.GD1468@sasha-vm> <20180501194450.GD10479@thunk.org> <20180501200019.GA7397@sasha-vm> <20180501205448.GE10479@thunk.org> <877eol808s.fsf@intel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2018-05-03 at 14:08 +0300, Jani Nikula wrote: > On Tue, 01 May 2018, "Theodore Y. Ts'o" wrote: > > Post -rc3 or -rc4, in my opinion bug fixes should wait until the > > next > > merge window before they get merged at all. > > What are -rc5 and later for then if not bug fixes? Baffled. They're definitely for bug fixes, but there's a spectrum: obvious bug fixes with no side effects are easy to justify. More complex bug fixes run the risk of having side effects which introduce other bugs, so could potentially destabilize the -rc process. In SCSI we tend to look at what the user visible effects of the bug are in the post -rc5 region and if they're slight or wouldn't be visible to most users, we'll hold them over. If the fix looks complex and we're not sure we caught the ramifications, we often add it to the merge window tree with a cc to stable and a note saying to wait X weeks before actually adding to the stable tree just to make sure no side effects show up with wider testing. So, as with most things, it's a judgment call for the maintainer. James