From: Andrew Morton <akpm@osdl.org>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org, hch@infradead.org
Subject: Re: [PATCH] Fix and add EXPORT_SYMBOL(filemap_write_and_wait)
Date: Sun, 23 Oct 2005 14:10:57 -0700 [thread overview]
Message-ID: <20051023141057.59e458f3.akpm@osdl.org> (raw)
In-Reply-To: <87ek6dtvxz.fsf@devron.myhome.or.jp>
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> wrote:
>
> This patch add EXPORT_SYMBOL(filemap_write_and_wait) and use it.
>
> See mm/filemap.c:
>
> And changes the filemap_write_and_wait() and filemap_write_and_wait_range().
>
> Current filemap_write_and_wait() doesn't wait if filemap_fdatawrite()
> returns error. However, even if filemap_fdatawrite() returns error, it
> may be submiting data pages . (e.g. in the case of -ENOSPC)
>
> However, even if filemap_fdatawrite() returned an error, it may have
> submitted the partially data pages to the device.
>
> I think we should wait those submitted data pages.
This behaviour is deliberate, although I wouldn't claim that a lot of
thought went into it.
If filemap_fdatawrite() returns an error, this might be due to some I/O
problem: dead disk, unplugged cable, etc. Given the generally crappy
quality of the kernel's handling of such exceptions, there's a good chance
that the filemap_fdatawait() will get stuck in D state forever.
I don't know how useful that really is - probably not very. Plus, yes, we
should wait on writeout after a -ENOSPC.
So hum, not sure. My gut feeling is that anything which we can do to help
the kernel limp along after an I/O error is a good thing, hence the
don't-wait-after-EIO feature should remain.
next prev parent reply other threads:[~2005-10-23 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-22 15:26 OGAWA Hirofumi
2005-10-23 21:10 ` Andrew Morton [this message]
2005-10-24 1:57 ` OGAWA Hirofumi
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=20051023141057.59e458f3.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome