Re: [patch] remove hugetlb syscalls

Jan Niehusmann
2002-11-16T18:16:36Z

On Thu, Nov 14, 2002 at 08:14:04PM +0000, Alan Cox wrote:
> On Thu, 2002-11-14 at 19:52, Alan Cox wrote:
> > On Thu, 2002-11-14 at 18:53, David Mosberger-Tang wrote:
> > > But that's excactly the point. The hugepage interface returns a
> > > different kind of virtual memory. There are tons of programs out
> > > there using mmap(). If such a program gets fed a path to the
> > > hugepagefs, it might end up with huge pages without knowing anything
> > > about huge pages. For the most part, that might work fine, but it
> > > could lead to subtle failures.
> >
> > Your argument makes sense. You are arguing
> Makes no sense rather 8)

Sorry, I didn't follow the whole discussion, so my argument may make no
sense at all, too. :-)

If I understand David correctly, he doesn't worry about programs that
want to use huge pages, but about programs just using mmap just to
access some file. If they get called with a file that behaves subtly
different than usual files, that may lead to failures or even security
holes.

But that's no argument to keep the syscalls, if you decide to implement
hugepagefs. The existance of the syscalls doesn't prevent bugs created
or triggered by hugepagefs.

Jan