linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
To: Vlastimil Babka <vbabka@suse.cz>, stable@vger.kernel.org
Cc: linux-mm@kvack.org, Roman Gushchin <guro@fb.com>
Subject: Re: [PATCH 4.19.y 2/2] mm: hide incomplete nr_indirectly_reclaimable in sysfs
Date: Tue, 9 Apr 2019 21:47:49 +0300	[thread overview]
Message-ID: <e87d3c53-c5e7-b828-5f15-850ca85e5446@yandex-team.ru> (raw)
In-Reply-To: <6a297270-5879-5a57-d41b-7d0629c53fd6@suse.cz>

On 09.04.2019 21:22, Vlastimil Babka wrote:
> On 4/9/19 7:05 PM, Konstantin Khlebnikov wrote:
>> This fixes /sys/devices/system/node/node*/vmstat format:
>>
>> ...
>> nr_dirtied 6613155
>> nr_written 5796802
>>   11089216
>> ...
>>
>> In upstream branch this fixed by commit b29940c1abd7 ("mm: rename and
>> change semantics of nr_indirectly_reclaimable_bytes").
>>
>> Cc: <stable@vger.kernel.org> # 4.19.y
> 
> So given the same circumstances as patch 1/2, shouldn't this also
> include 4.14.y ?

Oh, yes. Second patch should be applied for 4.14.y too.

> 
>> Fixes: 7aaf77272358 ("mm: don't show nr_indirectly_reclaimable in /proc/vmstat")
>> Signed-off-by: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
>> Cc: Roman Gushchin <guro@fb.com>
>> Cc: Vlastimil Babka <vbabka@suse.cz>
>> ---
>>   drivers/base/node.c |    7 ++++++-
>>   1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/base/node.c b/drivers/base/node.c
>> index 1ac4c36e13bb..c3968e2d0a98 100644
>> --- a/drivers/base/node.c
>> +++ b/drivers/base/node.c
>> @@ -197,11 +197,16 @@ static ssize_t node_read_vmstat(struct device *dev,
>>   			     sum_zone_numa_state(nid, i));
>>   #endif
>>   
>> -	for (i = 0; i < NR_VM_NODE_STAT_ITEMS; i++)
>> +	for (i = 0; i < NR_VM_NODE_STAT_ITEMS; i++) {
>> +		/* Skip hidden vmstat items. */
>> +		if (*vmstat_text[i + NR_VM_ZONE_STAT_ITEMS +
>> +				 NR_VM_NUMA_STAT_ITEMS] == '\0')
>> +			continue;
>>   		n += sprintf(buf+n, "%s %lu\n",
>>   			     vmstat_text[i + NR_VM_ZONE_STAT_ITEMS +
>>   			     NR_VM_NUMA_STAT_ITEMS],
>>   			     node_page_state(pgdat, i));
>> +	}
>>   
>>   	return n;
>>   }
>>
> 


  reply	other threads:[~2019-04-09 18:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 17:05 [PATCH 4.19.y 1/2] mm: hide incomplete nr_indirectly_reclaimable in /proc/zoneinfo Konstantin Khlebnikov
2019-04-09 17:05 ` [PATCH 4.19.y 2/2] mm: hide incomplete nr_indirectly_reclaimable in sysfs Konstantin Khlebnikov
2019-04-09 18:22   ` Vlastimil Babka
2019-04-09 18:47     ` Konstantin Khlebnikov [this message]
2019-04-18 15:55   ` Patch "[PATCH 4.19.y 2/2] mm: hide incomplete nr_indirectly_reclaimable in sysfs" has been added to the 4.14-stable tree gregkh
2019-04-18 15:56   ` Patch "[PATCH 4.19.y 2/2] mm: hide incomplete nr_indirectly_reclaimable in sysfs" has been added to the 4.19-stable tree gregkh
2019-04-18 15:58   ` [PATCH 4.19.y 2/2] mm: hide incomplete nr_indirectly_reclaimable in sysfs Greg KH
2019-04-09 18:21 ` [PATCH 4.19.y 1/2] mm: hide incomplete nr_indirectly_reclaimable in /proc/zoneinfo Vlastimil Babka
2019-04-18 15:58 ` Greg KH

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=e87d3c53-c5e7-b828-5f15-850ca85e5446@yandex-team.ru \
    --to=khlebnikov@yandex-team.ru \
    --cc=guro@fb.com \
    --cc=linux-mm@kvack.org \
    --cc=stable@vger.kernel.org \
    --cc=vbabka@suse.cz \
    /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