From: Andrea Arcangeli <aarcange@redhat.com>
To: lkp@lists.01.org
Subject: Re: [mm, page_alloc] 91727d2eac: WARNING: CPU: 0 PID: 65 at mm/memcontrol.c:998 mem_cgroup_update_lru_size+0xf0/0x106
Date: Wed, 21 Sep 2016 16:42:12 +0200 [thread overview]
Message-ID: <20160921144212.GX4716@redhat.com> (raw)
In-Reply-To: <20160921020912.GA22398@yexl-desktop>
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
On Wed, Sep 21, 2016 at 10:09:12AM +0800, kernel test robot wrote:
>
> FYI, we noticed the following commit:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/andrea/aa.git master
> commit 91727d2eac2b5800bda8d12c3007548c9e1196c8 ("Revert "mm, page_alloc: remove fair zone allocation policy"")
>
> in testcase: trinity
> with following parameters:
>
> runtime: 300s
Unless this happens also before or after all the reverts, I don't
think it's a concern. These reverts are in reverse-upstream order, so
it's probably a bisection problem that is inherited from how they were
applied upstream?
Maybe you could skip testing reverts of upstream patches to save
resources? And only test the commits before/after reverts of upstream
patches? (or the last one even if it's a revert)
prev parent reply other threads:[~2016-09-21 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 2:09 [mm, page_alloc] 91727d2eac: WARNING: CPU: 0 PID: 65 at mm/memcontrol.c:998 mem_cgroup_update_lru_size+0xf0/0x106 kernel test robot
2016-09-21 14:42 ` Andrea Arcangeli [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=20160921144212.GX4716@redhat.com \
--to=aarcange@redhat.com \
--cc=lkp@lists.01.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.