linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Shakeel Butt <shakeelb@google.com>
To: Michal Hocko <mhocko@suse.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux MM <linux-mm@kvack.org>,
	 bugzilla-daemon@bugzilla.kernel.org, vladi@aresgate.net,
	 Johannes Weiner <hannes@cmpxchg.org>,
	Roman Gushchin <guroan@gmail.com>
Subject: Re: [Bug 210075] New: [Thu Nov 5 13:14:27 2020] WARNING: CPU: 4 PID: 133 at mm/page_counter.c:57 page_counter_uncharge+0x34/0x40
Date: Mon, 9 Nov 2020 09:39:35 -0800	[thread overview]
Message-ID: <CALvZod7NyFv_9fKnmGJkH-oJrZEWE5H_zdEyjzqRx4NMntP61Q@mail.gmail.com> (raw)
In-Reply-To: <20201109081611.GF12240@dhcp22.suse.cz>

On Mon, Nov 9, 2020 at 12:16 AM Michal Hocko <mhocko@suse.com> wrote:
>
> [Cc Roman and Shakeel]
>
> On Fri 06-11-20 21:13:00, Andrew Morton wrote:
> > (switched to email.  Please respond via emailed reply-to-all, not via the
> > bugzilla web interface).
> >
> > On Thu, 05 Nov 2020 21:18:05 +0000 bugzilla-daemon@bugzilla.kernel.org wrote:
> >
> > > https://bugzilla.kernel.org/show_bug.cgi?id=210075
> > >
> > >             Bug ID: 210075
> > >            Summary: [Thu Nov  5 13:14:27 2020] WARNING: CPU: 4 PID: 133 at
> > >                     mm/page_counter.c:57 page_counter_uncharge+0x34/0x40
> > >            Product: Memory Management
> > >            Version: 2.5
> > >     Kernel Version: 5.9.5
> > >           Hardware: x86-64
> > >                 OS: Linux
> > >               Tree: Mainline
> > >             Status: NEW
> > >           Severity: normal
> > >           Priority: P1
> > >          Component: Page Allocator
> > >           Assignee: akpm@linux-foundation.org
> > >           Reporter: vladi@aresgate.net
> > >         Regression: No
> >
> > I'm assuming this is a bug in the networking code.  I've seen a number
> > of possibly-related emails fly past - is it familiar to anyone?
>
> Looks similar to 8de15e920dc8 ("mm: memcg: link page counters to root if
> use_hierarchy is false"). The path is different so the underlying reason
> might be something else.
>

The commit 8de15e920dc8 is not in 5.9.5.

Is the issue reproducible and bisectable?


      reply	other threads:[~2020-11-09 17:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-210075-27@https.bugzilla.kernel.org/>
2020-11-07  5:13 ` [Bug 210075] New: [Thu Nov 5 13:14:27 2020] WARNING: CPU: 4 PID: 133 at mm/page_counter.c:57 page_counter_uncharge+0x34/0x40 Andrew Morton
2020-11-08 17:49   ` Lorenzo Stoakes
2020-11-09  8:16   ` Michal Hocko
2020-11-09 17:39     ` Shakeel Butt [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=CALvZod7NyFv_9fKnmGJkH-oJrZEWE5H_zdEyjzqRx4NMntP61Q@mail.gmail.com \
    --to=shakeelb@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=guroan@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=vladi@aresgate.net \
    /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;
as well as URLs for NNTP newsgroup(s).