Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp4467992imm; Mon, 17 Sep 2018 14:37:09 -0700 (PDT) X-Google-Smtp-Source: ANB0VdYVWV6D7OVF1L1VvRaQWVPJhseAQKjoTVOlfhirjLLL2qrgQ1DLVR81gQ70xvbbn69DrDQC X-Received: by 2002:a63:2c01:: with SMTP id s1-v6mr22956406pgs.367.1537220229672; Mon, 17 Sep 2018 14:37:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537220229; cv=none; d=google.com; s=arc-20160816; b=OEpIh71ZA9vMxSwJ3Cd6oSlJWxueqA/IXE5OhAMInFnKt5CxyvZvA4A0D1u8MRbK2+ +Kq6VcTPJSYsju6azi/gu9bHCN0Fe4vKs7pxYSfoogOV7kVCoKvKzFsco2mkcA4Rqgow dCI4Hbu2CMpt/5yqannwj5GtD/YhNDDCYrLomosX0/gpk7RMToEtxNrx+EsD/QwDcub9 kvTZ/g6OEFT2qe4bc6W2gfLh40893g0xsJbfgizq8farFcOzpZXswHS+LU9Zi8n0+6ib 4EcmVEcgCYCJiXnes0ZdctUtSDgrBc2+cg0qBvWQlJpQXNQVXk9gEoTKqXbaKkAPX04b TEnw== 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:message-id:subject:cc:to:from:date; bh=FEgm0V5LhlwjvFkc5JVr/Ttyg5f1BzbsGmLVpdee59o=; b=awfdBFJGP0lJlU9Zwon18VWu0I5gl4G3bS9K0FPWdeskuIMVqkL56eFSQJdci9FwwW D/L5T39lH0422oVrTdCY27beXXwp71Gr1+9FOX6yMJayJUKfjT4/R9E/QVRS7+ud2PvP +yTkSIKD3RvKR6CxAgF00enMEzVzxYx4y3cYrLschyTZLMGYoLNaxvBqp0TH+twG1Kt2 Q8ggeH1iX4j1k3wWOX9V9HVmN953FzSoBJCrGGVN4TvMbHAtvHwVOYSS16+GfUIAGI1b 7UB5rvGbwcSBOZTaXr5RfoRC0YnarNt4LqDcAJy3tI6dJ/mttkDAY5FClAygsJS6kmAf AtKQ== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j3-v6si15807676pld.402.2018.09.17.14.36.54; Mon, 17 Sep 2018 14:37:09 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728656AbeIRDF0 (ORCPT + 99 others); Mon, 17 Sep 2018 23:05:26 -0400 Received: from mail.kernel.org ([198.145.29.99]:49736 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728644AbeIRDF0 (ORCPT ); Mon, 17 Sep 2018 23:05:26 -0400 Received: from gandalf.local.home (cpe-66-24-56-78.stny.res.rr.com [66.24.56.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id D14F820867; Mon, 17 Sep 2018 21:36:16 +0000 (UTC) Date: Mon, 17 Sep 2018 17:36:15 -0400 From: Steven Rostedt To: Vaibhav Nagarnaik Cc: linux-kernel@vger.kernel.org, Jason Behmer Subject: Re: [PATCH] ring-buffer: Allow for rescheduling when removing pages Message-ID: <20180917173615.7001c80c@gandalf.local.home> In-Reply-To: References: <20180907182131.144514-1-vnagarnaik@google.com> <20180907223129.71994-1-vnagarnaik@google.com> <20180917170055.1f1d161f@gandalf.local.home> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 17 Sep 2018 14:02:59 -0700 Vaibhav Nagarnaik wrote: > On Mon, Sep 17, 2018 at 2:01 PM Steven Rostedt wrote: > > > > On Mon, 17 Sep 2018 13:53:05 -0700 > > Vaibhav Nagarnaik wrote: > > > > > Hi Steven, > > > > > > Does the patch look good? Can this be picked up in the next rc? > > > > > > > Yes it's fine. I can pick it up. Does it need to be marked for stable? > > Thanks. > > It'd be great to be marked for stable, since older kernels are also > affected. But I can't judge if it crosses the threshold as a bug fix. > When backporting to stable I use two (admittedly subjective) metrics. One is the severity of the bug (this is low), the other is the risk of adding it (this is even lower). If the severity divided by the risk is high enough, I tag it for stable. Because the risk is so low, I have no problems with tagging it. Note, it will run through lots of tests before it gets out the door. -- Steve