linux-kernel - Re: [PATCH 1/2] mm/percpu.c: renew the max_contig if we merge the head and previous block.

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: <20140327145743.GC18503@htj.dyndns.org>
Date:	Thu, 27 Mar 2014 10:57:43 -0400
From:	Tejun Heo <tj@...nel.org>
To:	Jianyu Zhan <nasa4836@...il.com>
Cc:	linux-mm@...ck.org, akpm@...ux-foundation.org,
	cl@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] mm/percpu.c: renew the max_contig if we merge the
 head and previous block.

On Thu, Mar 27, 2014 at 07:05:43PM +0800, Jianyu Zhan wrote:
> During pcpu_alloc_area(), we might merge the current head with the
> previous block. Since we have calculated the max_contig using the
> size of previous block before we skip it, and now we update the size
> of previous block, so we should renew the max_contig.

pcpu_alloc_area() has been reimplemented in percpu/for-3.15.  Can you
please refresh the patch against the new implementation?

Thanks.

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