linux-kernel - Re: [RFC v5 PATCH 8/9] hugetlbfs: add hugetlbfs

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]

Date:	Mon, 27 Jul 2015 09:07:09 +0200
From:	Michal Hocko <mhocko@...nel.org>
To:	Mike Kravetz <mike.kravetz@...cle.com>
Cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	Dave Hansen <dave.hansen@...ux.intel.com>,
	Naoya Horiguchi <n-horiguchi@...jp.nec.com>,
	David Rientjes <rientjes@...gle.com>,
	Hugh Dickins <hughd@...gle.com>,
	Davidlohr Bueso <dave@...olabs.net>,
	Aneesh Kumar <aneesh.kumar@...ux.vnet.ibm.com>,
	Hillf Danton <hillf.zj@...baba-inc.com>,
	Christoph Hellwig <hch@...radead.org>
Subject: Re: [RFC v5 PATCH 8/9] hugetlbfs: add hugetlbfs_fallocate()

On Fri 24-07-15 09:18:35, Mike Kravetz wrote:
> On 07/23/2015 11:25 PM, Michal Hocko wrote:
> >I hope this is the current version of the pathc - I somehow got lost in
> >last submissions where the discussion happens in v4 thread. This version
> >seems to have the same issue:
> 
> Yes, Michal this issue exists in the version put into mmotm and was
> noticed by kbuild test robot and Stephen in linux-next build.
> 
> Your patch below is the most obvious.  Thanks!  However, is this
> the preferred method of handling this type of issue?  Is it
> preferred to create wrappers for the code which handles numa
> policy?

Yes that would be preferable. My "work around" was just to make my git
mirror of mmotm compilable. I am not sure whether Andrew picked my patch
but it will certainly get replaced by a cleaner version.
-- 
Michal Hocko
SUSE Labs
--
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/