From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kara Date: Wed, 31 Aug 2022 13:06:06 +0200 Subject: [Cluster-devel] [PATCH 11/14] ufs: replace ll_rw_block() In-Reply-To: <20220831072111.3569680-12-yi.zhang@huawei.com> References: <20220831072111.3569680-1-yi.zhang@huawei.com> <20220831072111.3569680-12-yi.zhang@huawei.com> Message-ID: <20220831110606.7c25xioli2uxcacr@quack3> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Wed 31-08-22 15:21:08, 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 ufs. > > Signed-off-by: Zhang Yi Looks good to me. Feel free to add: Reviewed-by: Jan Kara Honza > --- > fs/ufs/balloc.c | 4 +--- > 1 file changed, 1 insertion(+), 3 deletions(-) > > diff --git a/fs/ufs/balloc.c b/fs/ufs/balloc.c > index bd810d8239f2..bbc2159eece4 100644 > --- a/fs/ufs/balloc.c > +++ b/fs/ufs/balloc.c > @@ -296,9 +296,7 @@ static void ufs_change_blocknr(struct inode *inode, sector_t beg, > if (!buffer_mapped(bh)) > map_bh(bh, inode->i_sb, oldb + pos); > if (!buffer_uptodate(bh)) { > - ll_rw_block(REQ_OP_READ, 1, &bh); > - wait_on_buffer(bh); > - if (!buffer_uptodate(bh)) { > + if (bh_read(bh, 0)) { > ufs_error(inode->i_sb, __func__, > "read of block failed\n"); > break; > -- > 2.31.1 > -- Jan Kara SUSE Labs, CR