From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Berkhan, Enrik (GE Infra, Oil & Gas)" <enrik.berkhan@ge.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] fix 2.6.24-rc1 nfs_file_mmap change for NOMMU
Date: Wed, 12 Dec 2007 15:03:24 -0500 [thread overview]
Message-ID: <1197489804.9042.9.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <050A770C1DB41144817F02E395E493105257D4@FLRMLVEM02.e2k.ad.ge.com>
On Wed, 2007-12-12 at 08:29 +0100, Berkhan, Enrik (GE Infra, Oil & Gas)
wrote:
> Trond Myklebust wrote:
> > On Sun, 2007-12-09 at 19:52 +0100, Berkhan, Enrik (GE Infra, Oil & Gas)
> > wrote:
> >> - generic_file_mmap returns -ENOSYS for NOMMU systems; replicate this
> >> behaviour
> >
> > Why do that after going through the process of revalidating the inode
> > etc.? Just replace nfs_file_mmap() with a function returning ENOSYS in
> > the case of CONFIG_MMU.
> >
> > Better still, in the case of CONFIG_MMU, instead of having an
> > nfs_file_mmap(), just replace the .mmap field in nfs_file_operations
> > with a call to generic_file_mmap().
>
> I just tried to make it work without really knowing what I do :)
>
> I have mailed another patch implementing your second suggestion (the system
> still boots with nfsroot).
Thanks. That patch looks better. I have 2 questions, though:
1. Is this urgent enough to warrant pushing into 2.6.24?
2. Are there any filesystems which support mmap() on !CONFIG_MMU?
Cheers
Trond
prev parent reply other threads:[~2007-12-12 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 18:52 Berkhan, Enrik (GE Infra, Oil & Gas)
2007-12-12 2:40 ` Trond Myklebust
2007-12-12 7:29 ` Berkhan, Enrik (GE Infra, Oil & Gas)
2007-12-12 20:03 ` Trond Myklebust [this message]
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=1197489804.9042.9.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=enrik.berkhan@ge.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®