From: Al Viro <viro@ZenIV.linux.org.uk>
To: NeilBrown <neilb@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
David Herrmann <dh.herrmann@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Howells <dhowells@redhat.com>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH] fs: fix i_writecount on shmem and friends
Date: Fri, 14 Mar 2014 04:51:05 +0000 [thread overview]
Message-ID: <20140314045105.GN18016@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20140313165541.2b23dc96@notabene.brown>
On Thu, Mar 13, 2014 at 04:55:41PM +1100, NeilBrown wrote:
> Can we do direct writes from kernel space yet? If so I'll change the code to
> do that so that it will work with any filesystem (which supports direct
> writes).
You can - see __swap_writepage() (mm/page_io.c). However, that area is
about to get a lot of massage, so it would make sense to wait a bit...
> (The documentation says we that bitmap files should only be used on ext2 or
> ext3. Most people use bitmaps on the raw devices so hopefully the few who
> have a need for files will read the documentation :-)
>
> (and yes, I check for FMODE_WRITE)
Umm... Where?
prev parent reply other threads:[~2014-03-14 4:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 15:16 [PATCH] fs: fix i_writecount on shmem and friends David Herrmann
2014-03-11 19:05 ` Linus Torvalds
2014-03-12 18:19 ` Al Viro
2014-03-12 22:30 ` David Herrmann
2014-03-13 0:37 ` Al Viro
2014-03-13 0:37 ` Al Viro
2014-03-13 11:03 ` David Herrmann
2014-03-20 11:13 ` David Herrmann
2014-03-13 4:08 ` NeilBrown
2014-03-13 4:29 ` Al Viro
2014-03-13 5:55 ` NeilBrown
2014-03-14 4:51 ` Al Viro [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=20140314045105.GN18016@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=dh.herrmann@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=oleg@redhat.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.