From: "Robert W. Fuller" <orangemagicbus@sbcglobal.net>
To: linux-kernel@vger.kernel.org
Subject: why clear_buffer_uptodate in end_buffer_write_sync on write error?
Date: Sun, 02 Jan 2005 21:18:28 -0500 [thread overview]
Message-ID: <41D8AB74.7010409@sbcglobal.net> (raw)
I'm trying to understand the file systems. I'm making good progress,
but I don't get this. If the buffer is marked not up to date because
the write failed, won't this cause block_prepare_write to try and read
the buffer using ll_rw_block thereby overwriting the data that couldn't
be written? Is this desirable? Perhaps I'm confused?
next reply other threads:[~2005-01-03 2:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 2:18 Robert W. Fuller [this message]
2005-01-03 2:25 ` why clear_buffer_uptodate in end_buffer_write_sync on write error? Robert W. Fuller
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=41D8AB74.7010409@sbcglobal.net \
--to=orangemagicbus@sbcglobal.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.