linux-kernel - Re: [PATCH 1/3] mm: move inc_zone_page_state(NR

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: <20091015105154.C76A.A69D9226@jp.fujitsu.com>
Date:	Thu, 15 Oct 2009 10:54:32 +0900 (JST)
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	kosaki.motohiro@...fujitsu.com,
	LKML <linux-kernel@...r.kernel.org>,
	linux-mm <linux-mm@...ck.org>,
	Christoph Lameter <cl@...ux-foundation.org>, stable@...nel.org
Subject: Re: [PATCH 1/3] mm: move inc_zone_page_state(NR_ISOLATED) to just isolated place

> On Fri,  9 Oct 2009 10:06:58 +0900 (JST)
> KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> wrote:
> 
> > This patch series is trivial cleanup and fix of page migration.
> > 
> > 
> > ==========================================================
> > 
> > Christoph pointed out inc_zone_page_state(NR_ISOLATED) should be placed
> > in right after isolate_page().
> 
> The bugfixes are appropriate for 2.6.32 and should be backported into
> -stable too, I think.  I haven't checked to see how long those bugs
> have been present.
> 
> The cleanup is more appropriate for 2.6.33 so I had to switch the order
> of these patches.  Hopefully the bugfixes were not dependent on the
> cleanup.  

Yes, each patches are independent.
[1/3] is cleanup.
[2/3] and [3/3] are bugfixes.

I'm sorry for lack of prudence of patch order.



--
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/