All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: stable <stable@vger.kernel.org>
Subject: Re: Please add 17839856fd58 to the stable queue
Date: Mon, 15 Jun 2020 22:04:22 +0200	[thread overview]
Message-ID: <20200615200422.GA206959@kroah.com> (raw)
In-Reply-To: <CAHk-=wj-RATn3dNoBWgYaCSJGWotz3cRHFqWJwK-6GOLJK8o-w@mail.gmail.com>

On Mon, Jun 15, 2020 at 12:18:48PM -0700, Linus Torvalds wrote:
> Commit 17839856fd58 ("gup: document and work around "COW can break
> either way" issue") is a real fix, but wasn't marked for stable
> because I wanted it to get more coverage testing in mainline first.
> Not because the patch is all that complex or scary, but because I was
> worried we'd find some odd case where it would make things slower by
> triggering the GUP slowpath much more often due to people doing odd
> things.
> 
> It turns out my worry seems to have been misplaced. The kernel test
> robot did indeed trigger a case where this made a big difference, but
> rather than being bad, it improved the odd corner-case test-case
> performance by a factor of 20x by breaking the COW and triggering the
> fast-case code that way, rather than the other way around.
> 
> See
> 
>   https://lore.kernel.org/lkml/20200611040453.GK12456@shao2-debian/
> 
> for details.
> 
> So that commit fixes a bug, isn't expected to really make any
> difference on any sane workload, and can apparently help the crazy
> cases by a huge amount. Let's just push it to stable..

Will go do that now, was waiting to see if this caused any problems,
glad to see it hasn't.

greg k-h

      reply	other threads:[~2020-06-15 20:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 19:18 Please add 17839856fd58 to the stable queue Linus Torvalds
2020-06-15 20:04 ` Greg Kroah-Hartman [this message]

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=20200615200422.GA206959@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.