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] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 17 Dec 2010 16:28:51 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Andrea Arcangeli <aarcange@...hat.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: mmotm 2010-12-16-14-56 uploaded (hugetlb)

On 12/17/10 15:37, Andrea Arcangeli wrote:
> Hello,
> 
> On Fri, Dec 17, 2010 at 02:53:34PM -0800, Andrew Morton wrote:
>> afacit, CONFIG_HUGETLBFS must be enabled if CONFIG_HUGETLB_PAGE=y, and
>> thp-config_transparent_hugepage.patch broke that, by permitting
>> CONFIG_HUGETLBFS=n, CONFIG_HUGETLB_PAGE=y,
>> CONFIG_TRANSPARENT_HUGEPAGE=y.
> 
> CONFIG_HUGETLBFS and CONFIG_HUGETLB_PAGE existed before, and
> HUGETLBFS=n && HUGETLB_PAGE=y used to build just fine, I clearly
> didn't try a build with HUGETLBFS=n recently.
> 
>> There's lots of stuff in hugetlb.h which is clearly related to
>> hugetlbfs, but is enabled by CONFIG_HUGETLB_PAGE, so those things seem
>> to be pretty joined at the hip nowadays.
> 
> Yes, it used to build just fine but I guess after the last hugetlbfs
> updates I'm getting flood of errors no matter how I adjust things.
> hugetlbfs code who needs some fixup here.

I see a real *flood* of errors when I try building ARCH=um SUBARCH={i386|x86_64}:

> grep -c error: UM*/build*
UM32/build-defcfg.out:454539
UM64/build-defcfg.out:453707


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ