From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753391AbdHXRvV (ORCPT ); Thu, 24 Aug 2017 13:51:21 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59636 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751168AbdHXRvU (ORCPT ); Thu, 24 Aug 2017 13:51:20 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 9558A356F2 Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=longman@redhat.com Subject: Re: [PATCH] cpuset: Fix incorrect memory_pressure control file mapping To: Tejun Heo Cc: Li Zefan , Johannes Weiner , cgroups@vger.kernel.org, linux-kernel@vger.kernel.org References: <1503590669-16601-1-git-send-email-longman@redhat.com> <20170824164524.GR491396@devbig577.frc2.facebook.com> From: Waiman Long Organization: Red Hat Message-ID: Date: Thu, 24 Aug 2017 13:51:18 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <20170824164524.GR491396@devbig577.frc2.facebook.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Thu, 24 Aug 2017 17:51:19 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/24/2017 12:45 PM, Tejun Heo wrote: > On Thu, Aug 24, 2017 at 12:04:29PM -0400, Waiman Long wrote: >> 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 > Oops, applied to cgroup/for-4.13-fixes w/ stable cc'd. I broke it way > back in v4.4 which makes me wonder whether anybody is actually using > it. Probably not. Cheers, Longman