From: Christoph Hellwig <hch@infradead.org>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xip: export xip_file_fault
Date: Sat, 17 Sep 2011 09:53:47 -0400 [thread overview]
Message-ID: <20110917135346.GA31551@infradead.org> (raw)
In-Reply-To: <4E749003.30909@gmail.com>
On Sat, Sep 17, 2011 at 02:18:11PM +0200, Marco Stornelli wrote:
> From: Marco Stornelli <marco.stornelli@gmail.com>
>
> There aren't sufficient sync points for a fs for xip operations. In
> particular for the mmap case. It can be not sufficient to lock/unlock
> to do some operation inside get_xip_mem callback. For xip_file_read
> it's really easy to write a fs specific wrapper, xip_file_write hold
> i_mutex so no problem. With this patch it's possible to reuse the
> generic xip_file_fault, using a wrapper function in a fs, without to
> reinvent the wheel.
As usual please send patches to add exports only while adding callers
for it.
next prev parent reply other threads:[~2011-09-17 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-17 12:18 [PATCH] xip: export xip_file_fault Marco Stornelli
2011-09-17 13:53 ` Christoph Hellwig [this message]
2011-09-17 15:07 ` Marco Stornelli
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=20110917135346.GA31551@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).