From: Jan Kara <jack@suse.cz>
To: Anton Blanchard <anton@samba.org>
Cc: Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@lst.de>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jens Axboe <jens.axboe@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix regression in O_DIRECT|O_SYNC writes to block devices
Date: Thu, 22 Apr 2010 21:25:00 +0200 [thread overview]
Message-ID: <20100422192459.GF5805@quack.suse.cz> (raw)
In-Reply-To: <20100420023047.GN11751@kryten>
On Tue 20-04-10 12:30:47, Anton Blanchard wrote:
<snip>
> Signed-off-by: Anton Blanchard <anton@samba.org>
The patch looks good to me now.
Acked-by: Jan Kara <jack@suse.cz>
> Index: linux-2.6/fs/block_dev.c
> ===================================================================
> --- linux-2.6.orig/fs/block_dev.c 2010-04-20 11:28:32.000000000 +1000
> +++ linux-2.6/fs/block_dev.c 2010-04-20 11:36:46.000000000 +1000
> @@ -406,16 +406,23 @@ static loff_t block_llseek(struct file *
>
> int blkdev_fsync(struct file *filp, struct dentry *dentry, int datasync)
> {
> - struct block_device *bdev = I_BDEV(filp->f_mapping->host);
> + struct inode *bd_inode = filp->f_mapping->host;
> + struct block_device *bdev = I_BDEV(bd_inode);
> int error;
>
> - error = sync_blockdev(bdev);
> - if (error)
> - return error;
> -
> + /*
> + * There is no need to serialise calls to blkdev_issue_flush with
> + * i_mutex and doing so causes performance issues with concurrent
> + * O_SYNC writers to a block device.
> + */
> + mutex_unlock(&bd_inode->i_mutex);
> +
> error = blkdev_issue_flush(bdev, NULL);
> if (error == -EOPNOTSUPP)
> error = 0;
> +
> + mutex_lock(&bd_inode->i_mutex);
> +
> return error;
> }
> EXPORT_SYMBOL(blkdev_fsync);
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2010-04-22 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 4:40 Anton Blanchard
2010-04-15 8:47 ` Jan Kara
2010-04-15 10:04 ` Jens Axboe
2010-04-15 10:42 ` Christoph Hellwig
2010-04-15 13:34 ` Jan Kara
2010-04-20 2:26 ` Anton Blanchard
2010-04-20 2:30 ` Anton Blanchard
2010-04-22 19:25 ` Jan Kara [this message]
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=20100422192459.GF5805@quack.suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=hch@lst.de \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@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
Powered by JetHome