From: Andrew Morton <akpm@linux-foundation.org>
To: Theodore Tso <tytso@MIT.EDU>
Cc: jack@suse.cz, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, pavel@suse.cz
Subject: Re: [PATCH 2/2] ext2: Add blk_issue_flush() to syncing paths
Date: Wed, 14 Jan 2009 14:17:27 -0800 [thread overview]
Message-ID: <20090114141727.0a5dd3fb.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090114220418.GN6222@mit.edu>
On Wed, 14 Jan 2009 17:04:18 -0500
Theodore Tso <tytso@MIT.EDU> wrote:
> On Wed, Jan 14, 2009 at 10:18:34AM -0800, Andrew Morton wrote:
> > /**
> > * blkdev_issue_flush - queue a flush
> > * @bdev: blockdev to issue flush for
> > * @error_sector: error sector
> > *
> > * Description:
> > * Issue a flush for the block device in question. Caller can supply
> > * room for storing the error offset in case of a flush error, if they
> > * wish to. Caller must run wait_for_completion() on its own.
> > */
> >
> > So afaict the change you've made is incomplete. We'll queue a
> > writeback command to the disk but we won't wait for it to be sent down
> > the wire.
>
> No, that last part of the comment is stale, and it's already been
> confirmed by Jens. He's queued in the block tree:
>
> >From 801d773a6ff5dbb37c9eaa4b89ae3fc6574ba294 Mon Sep 17 00:00:00 2001
> From: Theodore Ts'o <tytso@mit.edu>
> Date: Tue, 13 Jan 2009 09:25:08 -0500
> Subject: [PATCH] block: Fix documentation for blkdev_issue_flush()
>
> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
> ---
> block/blk-barrier.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/block/blk-barrier.c b/block/blk-barrier.c
> index 8eba4e4..f7dae57 100644
> --- a/block/blk-barrier.c
> +++ b/block/blk-barrier.c
> @@ -302,7 +302,7 @@ static void bio_end_empty_barrier(struct bio *bio, int err)
> * Description:
> * Issue a flush for the block device in question. Caller can supply
> * room for storing the error offset in case of a flush error, if they
> - * wish to. Caller must run wait_for_completion() on its own.
> + * wish to.
> */
> int blkdev_issue_flush(struct block_device *bdev, sector_t *error_sector)
> {
<glances at the code>
<doh>
The function's name is now inappropriate.
next prev parent reply other threads:[~2009-01-14 22:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 15:12 [PATCH 1/2] ext2: Update also inode on disk when dir is IS_DIRSYNC Jan Kara
2009-01-14 15:12 ` [PATCH 2/2] ext2: Add blk_issue_flush() to syncing paths Jan Kara
2009-01-14 17:35 ` Eric Sandeen
2009-01-14 17:40 ` Jan Kara
2009-01-14 17:47 ` Eric Sandeen
2009-01-14 18:18 ` Andrew Morton
2009-01-14 18:27 ` Pavel Machek
2009-01-14 22:04 ` Theodore Tso
2009-01-14 22:17 ` Andrew Morton [this message]
2009-01-14 22:09 ` Theodore Tso
2009-01-14 22:26 ` Andrew Morton
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=20090114141727.0a5dd3fb.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=tytso@MIT.EDU \
/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