From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
"Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Jeff Layton <jlayton@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Muchun Song <songmuchun@bytedance.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Ira Weiny <ira.weiny@intel.com>
Subject: [PATCH 1/3] hfs: Unmap the page in the "fail_page" label
Date: Tue, 9 Aug 2022 17:20:02 +0200 [thread overview]
Message-ID: <20220809152004.9223-2-fmdefrancesco@gmail.com> (raw)
In-Reply-To: <20220809152004.9223-1-fmdefrancesco@gmail.com>
Several paths within hfs_btree_open() jump to the "fail_page" label
where put_page() is called while the page is still mapped.
Call kunmap() to unmap the page soon before put_page().
Reviewed-by: Ira Weiny <ira.weiny@intel.com>
Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
---
fs/hfs/btree.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/hfs/btree.c b/fs/hfs/btree.c
index 19017d296173..56c6782436e9 100644
--- a/fs/hfs/btree.c
+++ b/fs/hfs/btree.c
@@ -124,6 +124,7 @@ struct hfs_btree *hfs_btree_open(struct super_block *sb, u32 id, btree_keycmp ke
return tree;
fail_page:
+ kunmap(page);
put_page(page);
free_inode:
tree->inode->i_mapping->a_ops = &hfs_aops;
--
2.37.1
next prev parent reply other threads:[~2022-08-09 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 15:20 [PATCH 0/3] hfs: Replace kmap() with kmap_local_page() Fabio M. De Francesco
2022-08-09 15:20 ` Fabio M. De Francesco [this message]
2022-08-09 18:05 ` [PATCH 1/3] hfs: Unmap the page in the "fail_page" label Viacheslav Dubeyko
2022-08-09 15:20 ` [PATCH 2/3] hfs: Replace kmap() with kmap_local_page() in bnode.c Fabio M. De Francesco
2022-08-09 18:04 ` Viacheslav Dubeyko
2022-08-09 15:20 ` [PATCH 3/3] hfs: Replace kmap() with kmap_local_page() in btree.c Fabio M. De Francesco
2022-08-09 18:03 ` Viacheslav Dubeyko
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=20220809152004.9223-2-fmdefrancesco@gmail.com \
--to=fmdefrancesco@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=damien.lemoal@opensource.wdc.com \
--cc=ira.weiny@intel.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=songmuchun@bytedance.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).