From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, Waiman Long <longman@redhat.com>,
Tejun Heo <tj@kernel.org>
Subject: [PATCH 4.4 06/16] cpuset: Fix incorrect memory_pressure control file mapping
Date: Tue, 5 Sep 2017 09:09:56 +0200 [thread overview]
Message-ID: <20170905070904.730193171@linuxfoundation.org> (raw)
In-Reply-To: <20170905070904.465037171@linuxfoundation.org>
4.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Waiman Long <longman@redhat.com>
commit 1c08c22c874ac88799cab1f78c40f46110274915 upstream.
The memory_pressure control file was incorrectly set up without
a private value (0, by default). As a result, this control
file was treated like memory_migrate on read. By adding back the
FILE_MEMORY_PRESSURE private value, the correct memory pressure value
will be returned.
Signed-off-by: Waiman Long <longman@redhat.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Fixes: 7dbdb199d3bf ("cgroup: replace cftype->mode with CFTYPE_WORLD_WRITABLE")
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
kernel/cpuset.c | 1 +
1 file changed, 1 insertion(+)
--- a/kernel/cpuset.c
+++ b/kernel/cpuset.c
@@ -1910,6 +1910,7 @@ static struct cftype files[] = {
{
.name = "memory_pressure",
.read_u64 = cpuset_read_u64,
+ .private = FILE_MEMORY_PRESSURE,
},
{
next prev parent reply other threads:[~2017-09-05 7:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 7:09 [PATCH 4.4 00/16] 4.4.87-stable review Greg Kroah-Hartman
2017-09-05 7:09 ` [PATCH 4.4 01/16] irqchip: mips-gic: SYNC after enabling GIC region Greg Kroah-Hartman
2017-09-05 7:09 ` [PATCH 4.4 02/16] i2c: ismt: Dont duplicate the receive length for block reads Greg Kroah-Hartman
2017-09-05 7:09 ` [PATCH 4.4 03/16] i2c: ismt: Return EMSGSIZE for block reads with bogus length Greg Kroah-Hartman
2017-09-05 7:09 ` [PATCH 4.4 04/16] ceph: fix readpage from fscache Greg Kroah-Hartman
2017-09-05 7:09 ` [PATCH 4.4 05/16] cpumask: fix spurious cpumask_of_node() on non-NUMA multi-node configs Greg Kroah-Hartman
2017-09-05 7:09 ` Greg Kroah-Hartman [this message]
2017-09-05 7:09 ` [PATCH 4.4 07/16] alpha: uapi: Add support for __SANE_USERSPACE_TYPES__ Greg Kroah-Hartman
2017-09-05 7:09 ` [PATCH 4.4 08/16] CIFS: Fix maximum SMB2 header size Greg Kroah-Hartman
2017-09-05 7:09 ` [PATCH 4.4 09/16] CIFS: remove endian related sparse warning Greg Kroah-Hartman
2017-09-05 7:10 ` [PATCH 4.4 10/16] wl1251: add a missing spin_lock_init() Greg Kroah-Hartman
2017-09-05 7:10 ` [PATCH 4.4 11/16] xfrm: policy: check policy direction value Greg Kroah-Hartman
2017-09-05 7:10 ` [PATCH 4.4 14/16] kvm: arm/arm64: Force reading uncached stage2 PGD Greg Kroah-Hartman
2017-09-05 7:10 ` [PATCH 4.4 16/16] crypto: algif_skcipher - only call put_page on referenced and used pages Greg Kroah-Hartman
2017-09-05 16:47 ` [PATCH 4.4 00/16] 4.4.87-stable review Guenter Roeck
2017-09-05 17:12 ` Shuah Khan
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=20170905070904.730193171@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tj@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).