mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Vaibhav Nagarnaik <vnagarnaik@google.com>
Cc: linux-kernel@vger.kernel.org, Jason Behmer <jbehmer@google.com>
Subject: Re: [PATCH] ring-buffer: Allow for rescheduling when removing pages
Date: Mon, 17 Sep 2018 17:36:15 -0400	[thread overview]
Message-ID: <20180917173615.7001c80c@gandalf.local.home> (raw)
In-Reply-To: <CAL26m8L7f5iw_eNqbB2OVJX4vYebHcjiBJCQxyd_L4WjNFMb7A@mail.gmail.com>

On Mon, 17 Sep 2018 14:02:59 -0700
Vaibhav Nagarnaik <vnagarnaik@google.com> wrote:

> On Mon, Sep 17, 2018 at 2:01 PM Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > On Mon, 17 Sep 2018 13:53:05 -0700
> > Vaibhav Nagarnaik <vnagarnaik@google.com> 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

  reply	other threads:[~2018-09-17 21:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07 18:21 Vaibhav Nagarnaik
2018-09-07 18:30 ` Steven Rostedt
2018-09-07 19:28   ` Vaibhav Nagarnaik
2018-09-07 22:31 ` Vaibhav Nagarnaik
2018-09-17 20:53   ` Vaibhav Nagarnaik
2018-09-17 21:00     ` Steven Rostedt
2018-09-17 21:02       ` Vaibhav Nagarnaik
2018-09-17 21:36         ` Steven Rostedt [this message]
2018-09-17 21:42           ` Vaibhav Nagarnaik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180917173615.7001c80c@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=jbehmer@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vnagarnaik@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®