From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: "Lech Perczak" <l.perczak@camlintechnologies.com>,
"Al Viro" <viro@zeniv.linux.org.uk>,
"Eric Dumazet" <edumazet@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Piotr Figiel" <p.figiel@camlintechnologies.com>,
"Krzysztof Drobiński" <k.drobinski@camlintechnologies.com>,
"Pawel Lenkow" <p.lenkow@camlintechnologies.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Recurring warning in page_copy_sane (inside copy_page_to_iter) when running stress tests involving drop_caches
Date: Wed, 15 May 2019 17:37:38 +0200 [thread overview]
Message-ID: <20190515153738.GA27219@kroah.com> (raw)
In-Reply-To: <20190515152035.GE31704@bombadil.infradead.org>
On Wed, May 15, 2019 at 08:20:35AM -0700, Matthew Wilcox wrote:
> On Wed, May 15, 2019 at 05:04:06PM +0200, Greg Kroah-Hartman wrote:
> > > Greg, can you consider 6daef95b8c914866a46247232a048447fff97279 for
> > > backporting to stable? Nobody realised it was a bugfix at the time it
> > > went in. I suspect there aren't too many of us running HIGHMEM kernels
> > > any more.
> > >
> >
> > Sure, what kernel version(s) should this go to? 4.19 and newer?
>
> Looks like the problem was introduced with commit
> a90bcb86ae700c12432446c4aa1819e7b8e172ec so 4.14 and newer, I think.
Ok, I'll look into it after this round of stable kernels are released,
thanks.
greg k-h
next prev parent reply other threads:[~2019-05-15 15:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 9:25 Recurring warning in page_copy_sane (inside copy_page_to_iter) when running stress tests involving drop_caches Lech Perczak
2019-04-26 8:42 ` Lech Perczak
2019-05-15 13:18 ` Lech Perczak
2019-05-15 14:43 ` Matthew Wilcox
2019-05-15 15:02 ` Eric Dumazet
2019-05-15 15:18 ` Matthew Wilcox
2019-05-16 15:18 ` Lech Perczak
2019-05-15 15:04 ` Greg Kroah-Hartman
2019-05-15 15:20 ` Matthew Wilcox
2019-05-15 15:37 ` Greg Kroah-Hartman [this message]
2019-05-20 11:05 ` Greg Kroah-Hartman
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=20190515153738.GA27219@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=edumazet@google.com \
--cc=k.drobinski@camlintechnologies.com \
--cc=l.perczak@camlintechnologies.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=p.figiel@camlintechnologies.com \
--cc=p.lenkow@camlintechnologies.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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.