ocfs2-devel.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jan Kara via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: Zhang Yi <yi.zhang@huawei.com>
Cc: axboe@kernel.dk, almaz.alexandrovich@paragon-software.com,
	ntfs3@lists.linux.dev, jack@suse.cz, agruenba@redhat.com,
	hch@infradead.org, chengzhihao1@huawei.com,
	linux-kernel@vger.kernel.org, reiserfs-devel@vger.kernel.org,
	cluster-devel@redhat.com, rpeterso@redhat.com,
	viro@zeniv.linux.org.uk, yukuai3@huawei.com,
	linux-fsdevel@vger.kernel.org, tytso@mit.edu,
	linux-ext4@vger.kernel.org, dushistov@mail.ru,
	ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] [PATCH 07/14] ntfs3: replace ll_rw_block()
Date: Wed, 31 Aug 2022 12:59:13 +0200	[thread overview]
Message-ID: <20220831105913.ges3eatp5buz3bkh@quack3> (raw)
In-Reply-To: <20220831072111.3569680-8-yi.zhang@huawei.com>

On Wed 31-08-22 15:21:04, Zhang Yi wrote:
> ll_rw_block() is not safe for the sync read path because it cannot
> guarantee that submitting read IO if the buffer has been locked. We
> could get false positive EIO after wait_on_buffer() if the buffer has
> been locked by others. So stop using ll_rw_block() in
> ntfs_get_block_vbo().
> 
> Signed-off-by: Zhang Yi <yi.zhang@huawei.com>

Looks good to me. Feel free to add:

Reviewed-by: Jan Kara <jack@suse.cz>

								Honza

> ---
>  fs/ntfs3/inode.c | 7 ++-----
>  1 file changed, 2 insertions(+), 5 deletions(-)
> 
> diff --git a/fs/ntfs3/inode.c b/fs/ntfs3/inode.c
> index 51363d4e8636..bbe7d4ea1750 100644
> --- a/fs/ntfs3/inode.c
> +++ b/fs/ntfs3/inode.c
> @@ -630,12 +630,9 @@ static noinline int ntfs_get_block_vbo(struct inode *inode, u64 vbo,
>  			bh->b_size = block_size;
>  			off = vbo & (PAGE_SIZE - 1);
>  			set_bh_page(bh, page, off);
> -			ll_rw_block(REQ_OP_READ, 1, &bh);
> -			wait_on_buffer(bh);
> -			if (!buffer_uptodate(bh)) {
> -				err = -EIO;
> +			err = bh_read(bh, 0);
> +			if (err)
>  				goto out;
> -			}
>  			zero_user_segment(page, off + voff, off + block_size);
>  		}
>  	}
> -- 
> 2.31.1
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel

  parent reply	other threads:[~2022-08-31 10:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220831072111.3569680-1-yi.zhang@huawei.com>
     [not found] ` <20220831072111.3569680-2-yi.zhang@huawei.com>
2022-08-31 10:39   ` [Ocfs2-devel] [PATCH 01/14] fs/buffer: remove __breadahead_gfp() Jan Kara via Ocfs2-devel
     [not found] ` <20220831072111.3569680-4-yi.zhang@huawei.com>
2022-08-31 10:51   ` [Ocfs2-devel] [PATCH 03/14] fs/buffer: replace ll_rw_block() Jan Kara via Ocfs2-devel
     [not found] ` <20220831072111.3569680-5-yi.zhang@huawei.com>
2022-08-31 10:52   ` [Ocfs2-devel] [PATCH 04/14] gfs2: " Jan Kara via Ocfs2-devel
     [not found] ` <20220831072111.3569680-6-yi.zhang@huawei.com>
2022-08-31 10:53   ` [Ocfs2-devel] [PATCH 05/14] isofs: " Jan Kara via Ocfs2-devel
     [not found] ` <20220831072111.3569680-7-yi.zhang@huawei.com>
2022-08-31 10:58   ` [Ocfs2-devel] [PATCH 06/14] jbd2: " Jan Kara via Ocfs2-devel
     [not found] ` <20220831072111.3569680-8-yi.zhang@huawei.com>
2022-08-31 10:59   ` Jan Kara via Ocfs2-devel [this message]
     [not found] ` <20220831072111.3569680-10-yi.zhang@huawei.com>
2022-08-31 11:04   ` [Ocfs2-devel] [PATCH 09/14] reiserfs: " Jan Kara via Ocfs2-devel
     [not found] ` <20220831072111.3569680-11-yi.zhang@huawei.com>
2022-08-31 11:05   ` [Ocfs2-devel] [PATCH 10/14] udf: " Jan Kara via Ocfs2-devel
     [not found] ` <20220831072111.3569680-12-yi.zhang@huawei.com>
2022-08-31 11:06   ` [Ocfs2-devel] [PATCH 11/14] ufs: " Jan Kara via Ocfs2-devel
     [not found] ` <20220831072111.3569680-13-yi.zhang@huawei.com>
2022-08-31 11:06   ` [Ocfs2-devel] [PATCH 12/14] fs/buffer: remove ll_rw_block() helper Jan Kara via Ocfs2-devel
     [not found] ` <20220831072111.3569680-14-yi.zhang@huawei.com>
2022-08-31 11:15   ` [Ocfs2-devel] [PATCH 13/14] ext2: replace bh_submit_read() helper with bh_read_locked() Jan Kara via Ocfs2-devel
     [not found] ` <20220831072111.3569680-15-yi.zhang@huawei.com>
2022-08-31 11:16   ` [Ocfs2-devel] [PATCH 14/14] fs/buffer: remove bh_submit_read() helper Jan Kara via Ocfs2-devel
     [not found] ` <20220831072111.3569680-3-yi.zhang@huawei.com>
2022-08-31 11:30   ` [Ocfs2-devel] [PATCH 02/14] fs/buffer: add some new buffer read helpers Jan Kara via Ocfs2-devel
     [not found] ` <20220831072111.3569680-9-yi.zhang@huawei.com>
2022-08-31 11:31   ` [Ocfs2-devel] [PATCH 08/14] ocfs2: replace ll_rw_block() Jan Kara via Ocfs2-devel

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=20220831105913.ges3eatp5buz3bkh@quack3 \
    --to=ocfs2-devel@oss.oracle.com \
    --cc=agruenba@redhat.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=axboe@kernel.dk \
    --cc=chengzhihao1@huawei.com \
    --cc=cluster-devel@redhat.com \
    --cc=dushistov@mail.ru \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=rpeterso@redhat.com \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai3@huawei.com \
    /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).