From: Christoph Hellwig <hch@infradead.org>
To: mfasheh@suse.com, jlbec@evilplan.org
Cc: linux-fsdevel@vger.kernel.org
Subject: write_inode_now in ocfs2_cleanup_delete_inode
Date: Mon, 7 Nov 2011 05:49:01 -0500 [thread overview]
Message-ID: <20111107104901.GA1125@infradead.org> (raw)
It seems like that function only uses write_inode_now to write out
file data. Any chance you could switch to simply using
filemap_write_and_wait here?
next reply other threads:[~2011-11-07 10:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 10:49 Christoph Hellwig [this message]
2011-11-07 23:20 ` write_inode_now in ocfs2_cleanup_delete_inode Jan Kara
2011-11-17 10:20 ` Joel Becker
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=20111107104901.GA1125@infradead.org \
--to=hch@infradead.org \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mfasheh@suse.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).