From: Chao Yu <yuchao0@huawei.com>
To: Damien Le Moal <Damien.LeMoal@wdc.com>,
Naohiro Aota <Naohiro.Aota@wdc.com>,
"jth@kernel.org" <jth@kernel.org>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"chao@kernel.org" <chao@kernel.org>
Subject: Re: [PATCH] zonefs: fix to update .i_wr_refcnt correctly in zonefs_open_zone()
Date: Wed, 17 Mar 2021 08:56:14 +0800 [thread overview]
Message-ID: <64952e0e-0bd8-cbb2-9400-b4c16a886eee@huawei.com> (raw)
In-Reply-To: <BL0PR04MB65145B310933D52C432DA7BAE76B9@BL0PR04MB6514.namprd04.prod.outlook.com>
On 2021/3/17 7:30, Damien Le Moal wrote:
> On 2021/03/16 21:30, Chao Yu wrote:
>> In zonefs_open_zone(), if opened zone count is larger than
>> .s_max_open_zones threshold, we missed to recover .i_wr_refcnt,
>> fix this.
>>
>> Fixes: b5c00e975779 ("zonefs: open/close zone on file open/close")
>> Signed-off-by: Chao Yu <yuchao0@huawei.com>
>> ---
>> fs/zonefs/super.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/zonefs/super.c b/fs/zonefs/super.c
>> index 0fe76f376dee..be6b99f7de74 100644
>> --- a/fs/zonefs/super.c
>> +++ b/fs/zonefs/super.c
>> @@ -966,8 +966,7 @@ static int zonefs_open_zone(struct inode *inode)
>>
>> mutex_lock(&zi->i_truncate_mutex);
>>
>> - zi->i_wr_refcnt++;
>> - if (zi->i_wr_refcnt == 1) {
>> + if (zi->i_wr_refcnt == 0) {
>
> Nit: if (!zi->i_wr_refcnt) ? I can change that when applying.
More clean, thanks. :)
Thanks,
>
>>
>> if (atomic_inc_return(&sbi->s_open_zones) > sbi->s_max_open_zones) {
>> atomic_dec(&sbi->s_open_zones);
>> @@ -978,7 +977,6 @@ static int zonefs_open_zone(struct inode *inode)
>> if (i_size_read(inode) < zi->i_max_size) {
>> ret = zonefs_zone_mgmt(inode, REQ_OP_ZONE_OPEN);
>> if (ret) {
>> - zi->i_wr_refcnt--;
>> atomic_dec(&sbi->s_open_zones);
>> goto unlock;
>> }
>> @@ -986,6 +984,8 @@ static int zonefs_open_zone(struct inode *inode)
>> }
>> }
>>
>> + zi->i_wr_refcnt++;
>> +
>> unlock:
>> mutex_unlock(&zi->i_truncate_mutex);
>>
>>
>
> Good catch ! Will apply this and check zonefs test suite as this bug went
> undetected.
>
> Thanks.
>
prev parent reply other threads:[~2021-03-17 0:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 12:30 Chao Yu
2021-03-16 23:30 ` Damien Le Moal
2021-03-17 0:56 ` Chao Yu [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=64952e0e-0bd8-cbb2-9400-b4c16a886eee@huawei.com \
--to=yuchao0@huawei.com \
--cc=Damien.LeMoal@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=chao@kernel.org \
--cc=jth@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®