linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	Dong Aisheng <dongas86@gmail.com>,
	viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.or>,
	Dong Aisheng-B29396 <b29396@freescale.com>,
	r64343@freescale.com
Subject: Re: WARNING: at fs/fs-writeback.c when plug out SD card after system suspend/resume
Date: Thu, 4 Dec 2014 09:16:25 -0500	[thread overview]
Message-ID: <20141204141625.GA15219@htj.dyndns.org> (raw)
In-Reply-To: <20141204140835.GA15108@quack.suse.cz>

Hello,

On Thu, Dec 04, 2014 at 03:08:35PM +0100, Jan Kara wrote:
>   Yeah, but for the filesystem on top it doesn't really matter. Filesystems
> simply don't expect underlying structures can disappear. Changing all
> filesystems to deal with that would be too difficult so we have to make bdi
> stay in memory as needed and just detach it from the device (request queue)
> which goes away.

Wouldn't it be better to concentrate lifetime management to
request_queue instead of inserting another severance layer between bdi
and request_queue?

Thanks.

-- 
tejun

  reply	other threads:[~2014-12-04 14:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04  3:43 WARNING: at fs/fs-writeback.c when plug out SD card after system suspend/resume Dong Aisheng
2014-12-04 12:41 ` Jan Kara
2014-12-04 13:09   ` Christoph Hellwig
2014-12-04 13:36   ` Ulf Hansson
2014-12-04 14:08     ` Jan Kara
2014-12-04 14:16       ` Tejun Heo [this message]
2014-12-04 14:31         ` Jan Kara
2014-12-05  2:54   ` Dong Aisheng
  -- strict thread matches above, loose matches on Subject: below --
2014-12-04  3:46 Dong Aisheng

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=20141204141625.GA15219@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=b29396@freescale.com \
    --cc=dongas86@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.or \
    --cc=r64343@freescale.com \
    --cc=ulf.hansson@linaro.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).