LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de> To: Jan Kara <jack@suse.cz> Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org, linux-mm@kvack.org, bfennema@falcon.csc.calpoly.edu Subject: Re: [vm] writing to UDF DVD+RW (/dev/sr0) while under memory pressure: box ==> doorstop Date: Thu, 10 Jan 2008 16:29:50 +0100 [thread overview] Message-ID: <1199978990.4196.53.camel@homer.simson.net> (raw) In-Reply-To: <20080110144123.GA12331@atrey.karlin.mff.cuni.cz> On Thu, 2008-01-10 at 15:41 +0100, Jan Kara wrote: > > On Wed, 09 Jan 2008 12:11:20 +0100 > > > > > > I wonder why UDF was doing a synchronous write in there. In fact I wonder > > why it's writing the inode at all? extN doesn't do that. If for some > > reason it really does want to make the inode immediately reclaimable then > > simply shoving it down into the /dev/hda1 pagecache should be sufficient > > (ie: what you did).. > Looking at the code, I think UDF change is correct. UDF has to call > write_inode_now() because by the time clear_inode() is called, inode is > already written by VFS and prepared to be freed. But then UDF modifies > it in udf_clear_inode() (removes preallocation) and for these changes to > get to disk you have to write the inode explicitely. > But there's really no need to wait on IO. We only have to copy all > data from inode structure into buffers and that happens even if we don't > wait on sync. Perhaps I should go ahead and submit it then. There are 5 other async callers as well, so VM/UDF reclaim buglet can die, and those others can get what they asked for with net diffstat of 0. Fix udf_clear_inode() to request asynchronous writeout in icache reclaim path, and ensure that write_inore_now() honors that request, lest allocators needlessly block on iprune_mutex. Signed-off-by: Mike Galbraith <efault@gmx.de> diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c index 0fca820..f1cce24 100644 --- a/fs/fs-writeback.c +++ b/fs/fs-writeback.c @@ -657,7 +657,7 @@ int write_inode_now(struct inode *inode, int sync) int ret; struct writeback_control wbc = { .nr_to_write = LONG_MAX, - .sync_mode = WB_SYNC_ALL, + .sync_mode = sync ? WB_SYNC_ALL : WB_SYNC_NONE, .range_start = 0, .range_end = LLONG_MAX, }; diff --git a/fs/udf/inode.c b/fs/udf/inode.c index 6ff8151..d1fc116 100644 --- a/fs/udf/inode.c +++ b/fs/udf/inode.c @@ -117,7 +117,7 @@ void udf_clear_inode(struct inode *inode) udf_discard_prealloc(inode); udf_truncate_tail_extent(inode); unlock_kernel(); - write_inode_now(inode, 1); + write_inode_now(inode, 0); } kfree(UDF_I_DATA(inode)); UDF_I_DATA(inode) = NULL;
next prev parent reply other threads:[~2008-01-10 16:30 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-04 11:46 [vm] writing to UDF DVD+RW (/dev/sr0) while under memory pressure: box ==> doorstop Mike Galbraith 2008-01-06 9:42 ` Mike Galbraith 2008-01-06 18:01 ` Mike Galbraith 2008-01-06 20:29 ` Andrew Morton 2008-01-07 5:33 ` Mike Galbraith 2008-01-07 5:55 ` Mike Galbraith 2008-01-08 11:05 ` Mike Galbraith 2008-01-08 11:38 ` Andrew Morton 2008-01-08 15:21 ` Mike Galbraith 2008-01-08 15:27 ` Mike Galbraith 2008-01-09 11:11 ` Mike Galbraith 2008-01-09 23:01 ` Andrew Morton 2008-01-10 4:21 ` Mike Galbraith 2008-01-10 14:41 ` Jan Kara 2008-01-10 15:29 ` Mike Galbraith [this message] 2008-01-10 17:16 ` Jan Kara
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=1199978990.4196.53.camel@homer.simson.net \ --to=efault@gmx.de \ --cc=akpm@linux-foundation.org \ --cc=bfennema@falcon.csc.calpoly.edu \ --cc=jack@suse.cz \ --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: linkBe 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).