From: Christoph Hellwig <hch@lst.de>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Christoph Hellwig <hch@lst.de>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernl.org,
linux-mm@kvack.org
Subject: Re: [PATCH] hugetlbfs: add llseek method
Date: Wed, 24 Sep 2008 21:00:43 +0200 [thread overview]
Message-ID: <20080924190043.GA2312@lst.de> (raw)
In-Reply-To: <20080922185624.GA26551@csn.ul.ie>
On Mon, Sep 22, 2008 at 07:56:25PM +0100, Mel Gorman wrote:
> On (08/09/08 19:46), Christoph Hellwig didst pronounce:
> > Hugetlbfs currently doesn't set a llseek method for regular files, which
> > means it will fall back to default_llseek. This means no one can seek
> > beyond 2 Gigabytes.
> >
>
> I took another look at this as it was pointed out to me by apw that this
> might be a SEEK_CUR vs SEEK_SET thing and also whether lseek() was the
> key. To use lseek though, the large file defines had to be used or it failed
> whether your patch was applied or not. The error as you'd expect is lseek()
> complaining that the type was too small.
>
> At the face of it, the patch seems sensible but it works whether it is set
> or not so clearly I'm still missing something. The second test I tried is
> below. In the unlikely event it makes a difference, I was testing on qemu
> for i386.
Sorry, my original description was complete bullsh*t ;-) The problem
is the inverse of what I wrote. With default_llseek you can seek
everywhere even if that's outside of the fs limit. This should give you
quite interesting results if you seek outside of what we can represent
page->index on 32bit platforms.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-09-24 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 17:46 Christoph Hellwig
2008-09-22 7:58 ` Mel Gorman
2008-09-22 18:56 ` Mel Gorman
2008-09-24 19:00 ` Christoph Hellwig [this message]
2008-09-25 1:15 ` Mel Gorman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080924190043.GA2312@lst.de \
--to=hch@lst.de \
--cc=linux-fsdevel@vger.kernl.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox