diff options
| author | Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com> | 2021-02-17 18:58:11 +0900 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2021-03-04 11:38:41 +0100 |
| commit | 834c7ec6af441a3630fc60d72522e06dc65003eb (patch) | |
| tree | 6cb247e936bb761f443f75106432e758bf34b9c1 /fs/zonefs | |
| parent | 4e6e00704f9d5b2029eb4608156a27e1e368b7f1 (diff) | |
| download | linux-stable-834c7ec6af441a3630fc60d72522e06dc65003eb.tar.gz linux-stable-834c7ec6af441a3630fc60d72522e06dc65003eb.tar.bz2 linux-stable-834c7ec6af441a3630fc60d72522e06dc65003eb.zip | |
zonefs: Fix file size of zones in full condition
commit 059c01039c0185dbee7ed080f1f2bd22cb1e4dab upstream.
Per ZBC/ZAC/ZNS specifications, write pointers may not have valid values
when zones are in full condition. However, when zonefs mounts a zoned
block device, zonefs refers write pointers to set file size even when
the zones are in full condition. This results in wrong file size. To fix
this, refer maximum file size in place of write pointers for zones in
full condition.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Fixes: 8dcc1a9d90c1 ("fs: New zonefs file system")
Cc: <stable@vger.kernel.org> # 5.6+
Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/zonefs')
| -rw-r--r-- | fs/zonefs/super.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/fs/zonefs/super.c b/fs/zonefs/super.c index bec47f2d074b..3fe933b1010c 100644 --- a/fs/zonefs/super.c +++ b/fs/zonefs/super.c @@ -250,6 +250,9 @@ static loff_t zonefs_check_zone_condition(struct inode *inode, } inode->i_mode &= ~0222; return i_size_read(inode); + case BLK_ZONE_COND_FULL: + /* The write pointer of full zones is invalid. */ + return zi->i_max_size; default: if (zi->i_ztype == ZONEFS_ZTYPE_CNV) return zi->i_max_size; |