linux-kernel - Re: Kernel Oops with shm namespace cleanups

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20070302000808.GE10643@holomorphy.com>
Date:	Thu, 1 Mar 2007 16:08:08 -0800
From:	Bill Irwin <bill.irwin@...cle.com>
To:	Adam Litke <agl@...ibm.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	akpm@...ux-foundation.org
Subject: Re: Kernel Oops with shm namespace cleanups

On Wed, Feb 28, 2007 at 02:13:29PM -0600, Adam Litke wrote:
> Hey.  While testing 2.6.21-rc2 with libhugetlbfs, the shm-fork test case
> causes the kernel to oops.  To reproduce:  Execute 'make check' in the
> latest libhugetlbfs source on a 2.6.21-rc2 kernel with 100 huge pages
> allocated.  Using fewer huge pages will likely also trigger the oops.
> Libhugetlbfs can be downloaded from:
> http://libhugetlbfs.ozlabs.org/snapshots/libhugetlbfs-dev-20070228.tar.gz

Looks like I should grab these testcases for the sake of due diligence
(not to say I intend to alter maintenance style from primarily review,
approval, and bugfixing, not that I've been doing as much of any of those
as I should). To which architectures and/or distributions have the
userspace bits been ported, or otherwise run/tested on? A quick sniff
test on an Altix suggests SLES and/or ia64 may trip up the scripts:
$ su -c "make check"
Password:
         VERSION
	 ./run_tests.sh: line 1: get_hugetlbfs_path: command not found
	 run_tests.sh: unable to find hugetlbfs mountpoint
	 make: *** [check] Error 1


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