[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220831072111.3569680-12-yi.zhang@huawei.com>
Date: Wed, 31 Aug 2022 15:21:08 +0800
From: Zhang Yi <yi.zhang@...wei.com>
To: <linux-ext4@...r.kernel.org>, <linux-fsdevel@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <cluster-devel@...hat.com>,
<ntfs3@...ts.linux.dev>, <ocfs2-devel@....oracle.com>,
<reiserfs-devel@...r.kernel.org>
CC: <jack@...e.cz>, <tytso@....edu>, <akpm@...ux-foundation.org>,
<axboe@...nel.dk>, <viro@...iv.linux.org.uk>,
<rpeterso@...hat.com>, <agruenba@...hat.com>,
<almaz.alexandrovich@...agon-software.com>, <mark@...heh.com>,
<dushistov@...l.ru>, <hch@...radead.org>, <yi.zhang@...wei.com>,
<chengzhihao1@...wei.com>, <yukuai3@...wei.com>
Subject: [PATCH 11/14] ufs: replace ll_rw_block()
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 <yi.zhang@...wei.com>
---
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
Powered by blists - more mailing lists