linux-kernel - Re: [BUGFIX] vmstat: fix dirty threshold ordering

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <AANLkTikQuhq0GMjiSUdctq_qSbJdZss_6pZkAZuF1Rck@mail.gmail.com>
Date:	Tue, 30 Nov 2010 12:55:48 +0900
From:	Minchan Kim <minchan.kim@...il.com>
To:	Wu Fengguang <fengguang.wu@...el.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Michael Rubin <mrubin@...gle.com>,
	Linux Memory Management List <linux-mm@...ck.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [BUGFIX] vmstat: fix dirty threshold ordering

On Mon, Nov 29, 2010 at 7:38 PM, Wu Fengguang <fengguang.wu@...el.com> wrote:
> The nr_dirty_[background_]threshold fields are misplaced before the
> numa_* fields, and users will read strange values.
>
> This is the right order. Before patch, nr_dirty_background_threshold
> will read as 0 (the value from numa_miss).
>
>        numa_hit 128501
>        numa_miss 0
>        numa_foreign 0
>        numa_interleave 7388
>        numa_local 128501
>        numa_other 0
>        nr_dirty_threshold 144291
>        nr_dirty_background_threshold 72145
>
> Cc: Michael Rubin <mrubin@...gle.com>
> Signed-off-by: Wu Fengguang <fengguang.wu@...el.com>
Reviewed-by: Minchan Kim <minchan.kim@...il.com>

-- 
Kind regards,
Minchan Kim
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/