linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: linux-fsdevel@vger.kernel.org
Cc: Wu Fengguang <fengguang.wu@intel.com>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	k-mio@sx.jp.nec.com, Andrew Morton <akpm@linux-foundation.org>,
	Christoph Hellwig <hch@infradead.org>
Subject: [PATCH 0/2] Make task doing heavy writing killable
Date: Mon, 14 Nov 2011 12:10:28 +0100	[thread overview]
Message-ID: <1321269030-6019-1-git-send-email-jack@suse.cz> (raw)


  Hello,

  these two patches aim at making task waiting in balance_dirty_pages()
killable.  This is desirable because otherwise if filesystem stops accepting
writes (e.g. if device has been removed or other serious error condidion) we
have a task stuck in D state forever.

  I'm not sure who should merge these two patches... Al, Fengguang?

									Honza

             reply	other threads:[~2011-11-14 11:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 11:10 Jan Kara [this message]
2011-11-14 11:10 ` [PATCH 1/2] mm: Make task in balance_dirty_pages() killable Jan Kara
2011-11-14 12:12   ` Wu Fengguang
2011-11-14 12:37     ` Jan Kara
2011-11-14 11:10 ` [PATCH 2/2] fs: Make write(2) interruptible by a signal Jan Kara
2011-11-14 12:12   ` Matthew Wilcox
2011-11-14 12:15   ` Wu Fengguang
2011-11-14 12:34     ` Jan Kara
2011-11-14 14:16       ` Matthew Wilcox
2011-11-14 15:30         ` Jan Kara
2011-11-14 18:44           ` Jeremy Allison
2011-11-14 11:59 ` [PATCH 0/2] Make task doing heavy writing killable Wu Fengguang
2011-11-14 12:05   ` Christoph Hellwig
2011-11-14 12:24     ` Jan Kara
2011-11-14 12:29     ` Wu Fengguang
2011-11-14 12:41       ` Christoph Hellwig
2011-11-14 13:01         ` Wu Fengguang
2011-11-14 15:28           ` Jan Kara
2011-11-14 15:32             ` Christoph Hellwig
2011-11-14 16:19               ` Jan Kara
2011-11-14 12:12   ` 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=1321269030-6019-1-git-send-email-jack@suse.cz \
    --to=jack@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=hch@infradead.org \
    --cc=k-mio@sx.jp.nec.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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).