[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220504153126.635564169@linuxfoundation.org>
Date: Wed, 4 May 2022 18:46:59 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-kernel@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
stable@...r.kernel.org,
Damien Le Moal <damien.lemoal@...nsource.wdc.com>,
Johannes Thumshirn <johannes.thumshirn@....com>,
Chaitanya Kulkarni <kch@...dia.com>,
Hans Holmberg <hans.holmberg@....com>
Subject: [PATCH 5.17 181/225] zonefs: Clear inode information flags on inode creation
From: Damien Le Moal <damien.lemoal@...nsource.wdc.com>
commit 694852ead287a3433126e7ebda397b242dc99624 upstream.
Ensure that the i_flags field of struct zonefs_inode_info is cleared to
0 when initializing a zone file inode, avoiding seeing the flag
ZONEFS_ZONE_OPEN being incorrectly set.
Fixes: b5c00e975779 ("zonefs: open/close zone on file open/close")
Cc: <stable@...r.kernel.org>
Signed-off-by: Damien Le Moal <damien.lemoal@...nsource.wdc.com>
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@....com>
Reviewed-by: Chaitanya Kulkarni <kch@...dia.com>
Reviewed-by: Hans Holmberg <hans.holmberg@....com>
Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
---
fs/zonefs/super.c | 1 +
1 file changed, 1 insertion(+)
--- a/fs/zonefs/super.c
+++ b/fs/zonefs/super.c
@@ -1155,6 +1155,7 @@ static struct inode *zonefs_alloc_inode(
inode_init_once(&zi->i_vnode);
mutex_init(&zi->i_truncate_mutex);
zi->i_wr_refcnt = 0;
+ zi->i_flags = 0;
return &zi->i_vnode;
}
Powered by blists - more mailing lists