From: Roman Gushchin <guro@fb.com>
To: Andrei Vagin <avagin@gmail.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: WARNING: CPU: 0 PID: 11655 at mm/page_counter.c:62
Date: Thu, 20 Jun 2019 01:32:43 +0000 [thread overview]
Message-ID: <20190620013227.GA27615@castle> (raw)
In-Reply-To: <CANaxB-xAjfpmLSVLMWb2EETQR5zroizJ9xjTNmTTARnJBSEYvA@mail.gmail.com>
On Wed, Jun 19, 2019 at 04:41:05PM -0700, Andrei Vagin wrote:
> On Wed, Jun 19, 2019 at 2:19 PM Roman Gushchin <guro@fb.com> wrote:
> >
> > On Tue, Jun 18, 2019 at 07:08:26PM -0700, Andrei Vagin wrote:
> > > Hello,
> > >
> > > We run CRIU tests on linux-next kernels and today we found this
> > > warning in the kernel log:
> >
> > Hello, Andrei!
> >
> > Can you, please, check if the following patch fixes the problem?
>
> All my tests passed: https://urldefense.proofpoint.com/v2/url?u=https-3A__travis-2Dci.org_avagin_linux_builds_547940031&d=DwIBaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=jJYgtDM7QT-W-Fz_d29HYQ&m=PL584FpQp6_68teeNmPDMBi6YNZHVSL9_X83jLmfid0&s=g-gMywZpFZp5GRfXixu-iX_YPx0rRrMhCgMZc-5IcF4&e=
>
> Tested-by: Andrei Vagin <avagin@gmail.com>
Thank you very much!
I'll send the proper patch soon. It's a bit different to what you've tested
(I realized that for root_mem_cgroup vmstats should be handled differently too).
So I won't put your tested-by for now, let's wait for tests passing with the
actual patch.
Thank you!
Roman
prev parent reply other threads:[~2019-06-20 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 2:08 Andrei Vagin
2019-06-19 3:41 ` Roman Gushchin
2019-06-19 21:19 ` Roman Gushchin
2019-06-19 23:41 ` Andrei Vagin
2019-06-20 1:32 ` Roman Gushchin [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=20190620013227.GA27615@castle \
--to=guro@fb.com \
--cc=avagin@gmail.com \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox