From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Cong Wang <amwang@redhat.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Hugh Dickins <hughd@google.com>,
linux-mm@kvack.org, Lennart Poettering <lennart@poettering.net>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: [Patch] tmpfs: add fallocate support
Date: Wed, 16 Nov 2011 15:21:55 -0800 [thread overview]
Message-ID: <1321485715.12374.56.camel@nimitz> (raw)
In-Reply-To: <4EC36494.30803@redhat.com>
On Wed, 2011-11-16 at 15:21 +0800, Cong Wang wrote:
> ao? 2011a1'11ae??16ae?JPY 01:43, Dave Hansen a??e??:
> > On Tue, 2011-11-15 at 18:23 +0800, Cong Wang wrote:
> >>> + if (!(mode& FALLOC_FL_KEEP_SIZE)) {
> >>> + ret = inode_newsize_ok(inode, (offset + len));
> >>> + if (ret)
> >>> + return ret;
> >>> + }
> >
> > inode_newsize_ok()'s comments say:
> >
> > * inode_newsize_ok must be called with i_mutex held.
> >
> > But I don't see any trace of it.
>
> Hmm, even for tmpfs? I see none of the tmpfs code takes
> i_mutex lock though...
Look harder. :)
ramfs/tmpfs for a large part just used the generic VFS functions to do
their work since they're page-cache based. For instance:
static const struct file_operations shmem_file_operations = {
...
.aio_write = generic_file_aio_write,
IOW, you need to check beyond mm/shmem.c.
-- Dave
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-11-16 23:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 8:42 [Patch] tmpfs: add fallocate support Amerigo Wang
2011-11-15 10:23 ` Cong Wang
2011-11-15 17:43 ` Dave Hansen
2011-11-16 7:21 ` Cong Wang
2011-11-16 23:21 ` Dave Hansen [this message]
2011-11-15 11:23 ` Pekka Enberg
2011-11-16 7:09 ` Cong Wang
2011-11-16 7:12 ` Pekka Enberg
2011-11-16 7:16 ` Cong Wang
2011-11-17 1:31 ` Hugh Dickins
2011-11-18 10:27 ` Cong Wang
2011-11-16 1:18 ` KAMEZAWA Hiroyuki
2011-11-16 7:12 ` Cong Wang
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=1321485715.12374.56.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=hughd@google.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=lennart@poettering.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).