From: Guillaume Morin <guillaume@morinfr.org>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
cgroups@vger.kernel.org, Mina Almasry <almasrymina@google.com>,
David Rientjes <rientjes@google.com>,
Greg Thelen <gthelen@google.com>,
Sandipan Das <sandipan@linux.ibm.com>,
Shakeel Butt <shakeelb@google.com>, Shuah Khan <shuah@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Guillaume Morin <guillaume@morinfr.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] hugetlb: fix hugetlb cgroup refcounting during vma split
Date: Tue, 31 Aug 2021 16:01:48 +0200 [thread overview]
Message-ID: <20210831140147.GA18648@bender.morinfr.org> (raw)
In-Reply-To: <20210830215015.155224-1-mike.kravetz@oracle.com>
On 30 Aug 14:50, Mike Kravetz wrote:
> Guillaume Morin reported hitting the following WARNING followed
> by GPF or NULL pointer deference either in cgroups_destroy or in
> the kill_css path.:
>
> percpu ref (css_release) <= 0 (-1) after switching to atomic
> WARNING: CPU: 23 PID: 130 at lib/percpu-refcount.c:196 percpu_ref_switch_to_atomic_rcu+0x127/0x130
> CPU: 23 PID: 130 Comm: ksoftirqd/23 Kdump: loaded Tainted: G O 5.10.60 #1
> RIP: 0010:percpu_ref_switch_to_atomic_rcu+0x127/0x130
> Call Trace:
> rcu_core+0x30f/0x530
> rcu_core_si+0xe/0x10
> __do_softirq+0x103/0x2a2
> ? sort_range+0x30/0x30
> run_ksoftirqd+0x2b/0x40
> smpboot_thread_fn+0x11a/0x170
> kthread+0x10a/0x140
> ? kthread_create_worker_on_cpu+0x70/0x70
> ret_from_fork+0x22/0x30
>
> Upon further examination, it was discovered that the css structure
> was associated with hugetlb reservations.
>
> For private hugetlb mappings the vma points to a reserve map that
> contains a pointer to the css. At mmap time, reservations are set up
> and a reference to the css is taken. This reference is dropped in the
> vma close operation; hugetlb_vm_op_close. However, if a vma is split
> no additional reference to the css is taken yet hugetlb_vm_op_close will
> be called twice for the split vma resulting in an underflow.
>
> Fix by taking another reference in hugetlb_vm_op_open. Note that the
> reference is only taken for the owner of the reserve map. In the more
> common fork case, the pointer to the reserve map is cleared for
> non-owning vmas.
>
> Fixes: e9fe92ae0cd2 ("hugetlb_cgroup: add reservation accounting for
> private mappings")
> Reported-by: Guillaume Morin <guillaume@morinfr.org>
> Suggested-by: Guillaume Morin <guillaume@morinfr.org>
> Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com>
> Cc: <stable@vger.kernel.org>
I verified that the patch does fix the underflow. I appreciate the help!
Feel free to add:
Tested-by: Guillaume Morin <guillaume@morinfr.org>
--
Guillaume Morin <guillaume@morinfr.org>
prev parent reply other threads:[~2021-08-31 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 21:50 [PATCH] hugetlb: fix hugetlb cgroup refcounting during vma split Mike Kravetz
2021-08-31 14:01 ` Guillaume Morin [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=20210831140147.GA18648@bender.morinfr.org \
--to=guillaume@morinfr.org \
--cc=akpm@linux-foundation.org \
--cc=almasrymina@google.com \
--cc=cgroups@vger.kernel.org \
--cc=gthelen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=rientjes@google.com \
--cc=sandipan@linux.ibm.com \
--cc=shakeelb@google.com \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).