[Libhugetlbfs-devel] Only i386 needs __syscall_return macro for unmapped zone debugging

2006-10-26 Thread David Gibson
Adam, please apply. At present, we disable the functions for producing debugging output if the __syscall_return macro is not available. However, we only actually need the __syscall_return macro on i386, in order to redefine some of the other _syscall*() macro because the standard versions don't w

Re: [Libhugetlbfs-devel] [PATCH] add security section to README

2006-10-26 Thread David Gibson
On Thu, Oct 26, 2006 at 03:04:58PM -0500, Steve Fox wrote: > On Thu, 2006-10-26 at 14:48 -0500, Adam Litke wrote: > > I think the part about mount point permissions should be revised for > > clarity. How about the following? : > > > > We recommend creating your hugetlbfs mount point with restrict

[Libhugetlbfs-devel] [PATCH] hugetlbd: Move socket to /var/run

2006-10-26 Thread Adam Litke
socket to /var/run to avoid this problem. Note that on most systems, hugetlbd will need to be run as root in order to create the socket in the more secure /var/run directory. Signed-off-by: Adam Litke <[EMAIL PROTECTED]> diff -purN libhugetlbfs-dev-20061026.orig/hugetlbd.c libhugetlb

[Libhugetlbfs-devel] NEWS file for 1.0.1

2006-10-26 Thread Steve Fox
Adam didn't propose anything clever for the release name, so here's my suggestion :) Signed-off-by: Steve Fox <[EMAIL PROTECTED]> --- libhugetlbfs 1.0.1 "Spicy Garlic" == This small maintenance release brings a security fix, a few

Re: [Libhugetlbfs-devel] [PATCH] add security section to README

2006-10-26 Thread Steve Fox
On Thu, 2006-10-26 at 14:48 -0500, Adam Litke wrote: > I think the part about mount point permissions should be revised for > clarity. How about the following? : > > We recommend creating your hugetlbfs mount point with restricted > permissions that permit only a specific user or group to access

Re: [Libhugetlbfs-devel] [PATCH] add security section to README

2006-10-26 Thread Adam Litke
On Thu, 2006-10-26 at 14:33 -0500, Steve Fox wrote: > docs: Add security section to README > > Signed-off-by: Steve Fox <[EMAIL PROTECTED]> > --- > > diff --git a/README b/README > index bff0b68..88b2b16 100644 > --- a/README > +++ b/README > @@ -40,3 +40,14 @@ (including all libhugetlbfs debug o

[Libhugetlbfs-devel] [PATCH] add security section to README

2006-10-26 Thread Steve Fox
docs: Add security section to README Signed-off-by: Steve Fox <[EMAIL PROTECTED]> --- diff --git a/README b/README index bff0b68..88b2b16 100644 --- a/README +++ b/README @@ -40,3 +40,14 @@ (including all libhugetlbfs debug output libhugetlbfs-devel@lists.sourceforge.net and we'll help out as mu

Re: [Libhugetlbfs-devel] [PATCH] ldscripts: Missing bss section placement statement

2006-10-26 Thread Adam Litke
On Thu, 2006-10-26 at 10:35 +1000, David Gibson wrote: > On Wed, Oct 25, 2006 at 01:46:28PM -0500, Adam Litke wrote: > > ldscripts: Missing bss section placement statement > > > > This appears to be a longstanding bug in the ppc32 .xB linker script. When > > the > > BSS was moved into its own ht

Re: [Libhugetlbfs-devel] Improved exorcism

2006-10-26 Thread David Gibson
Latest version of the daemon killing patch. I've cleaned up the previously rather contorted code paths for sharing in elflink.c. Next step per-user hugetlbfs directories. For sure, this time ;-). Index: libhugetlbfs/HOWTO === --- l