On Mon, Sep 17, 2018 at 2:36 PM Steven Rostedt <rost...@goodmis.org> wrote: > > On Mon, 17 Sep 2018 14:02:59 -0700 > Vaibhav Nagarnaik <vnagarn...@google.com> wrote: > > > On Mon, Sep 17, 2018 at 2:01 PM Steven Rostedt <rost...@goodmis.org> wrote: > > > > > > On Mon, 17 Sep 2018 13:53:05 -0700 > > > Vaibhav Nagarnaik <vnagarn...@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.
I think it's low risk as well. Let's mark it for stable. Thanks Vaibhav > -- Steve
smime.p7s
Description: S/MIME Cryptographic Signature