From: Sergei Antonov <saproj@gmail.com>
To: linux-fsdevel@vger.kernel.org, Sasha Levin <sasha.levin@oracle.com>
Cc: Anton Altaparmakov <aia21@cam.ac.uk>,
Al Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Vyacheslav Dubeyko <slava@dubeyko.com>,
Hin-Tak Leung <htl10@users.sourceforge.net>,
Sougata Santra <sougata@tuxera.com>,
Sergei Antonov <saproj@gmail.com>
Subject: [PATCH] hfsplus: release bnode pages after use, not before
Date: Sun, 7 Jun 2015 02:42:56 +0200 [thread overview]
Message-ID: <1433637776-3559-1-git-send-email-saproj@gmail.com> (raw)
Fix this bugreport by Sasha Levin:
http://lkml.org/lkml/2015/2/20/85 ("use after free")
Make sure mapped pages are available for the entire lifetime of hfs_bnode.
Cc: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Vyacheslav Dubeyko <slava@dubeyko.com>
Cc: Hin-Tak Leung <htl10@users.sourceforge.net>
Cc: Sougata Santra <sougata@tuxera.com>
Reported-by: Sasha Levin <sasha.levin@oracle.com>
Signed-off-by: Sergei Antonov <saproj@gmail.com>
---
fs/hfsplus/bnode.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/fs/hfsplus/bnode.c b/fs/hfsplus/bnode.c
index 759708f..5af50fb 100644
--- a/fs/hfsplus/bnode.c
+++ b/fs/hfsplus/bnode.c
@@ -454,7 +454,6 @@ static struct hfs_bnode *__hfs_bnode_create(struct hfs_btree *tree, u32 cnid)
page_cache_release(page);
goto fail;
}
- page_cache_release(page);
node->page[i] = page;
}
@@ -566,13 +565,12 @@ node_error:
void hfs_bnode_free(struct hfs_bnode *node)
{
-#if 0
int i;
- for (i = 0; i < node->tree->pages_per_bnode; i++)
+ for (i = 0; i < node->tree->pages_per_bnode; i++) {
if (node->page[i])
page_cache_release(node->page[i]);
-#endif
+ }
kfree(node);
}
--
2.3.0
next reply other threads:[~2015-06-06 22:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-07 0:42 Sergei Antonov [this message]
2015-06-08 15:45 ` [PATCH] hfsplus: release bnode pages after use, not before Vyacheslav Dubeyko
2015-06-08 16:32 ` Sergei Antonov
2015-06-08 16:45 ` Viacheslav Dubeyko
2015-06-08 16:50 ` Sergei Antonov
2015-06-09 22:15 ` Andrew Morton
2015-06-09 23:00 ` Anton Altaparmakov
2015-06-09 23:08 ` Anton Altaparmakov
2015-06-09 23:16 ` Andrew Morton
2015-06-09 23:34 ` Anton Altaparmakov
2015-06-09 23:23 ` Anton Altaparmakov
2015-06-09 23:40 ` Sergei Antonov
2015-06-14 2:27 ` Hin-Tak Leung
2015-06-14 14:18 ` Sergei Antonov
2015-06-17 23:26 ` Hin-Tak Leung
2015-06-18 13:09 ` Sergei Antonov
2015-06-09 18:06 ` Anton Altaparmakov
[not found] <1433781680.24509.YahooMailBasic@web172301.mail.ir2.yahoo.com>
2015-06-08 16:47 ` Sergei Antonov
[not found] <1434584504.1063.YahooMailBasic@web172304.mail.ir2.yahoo.com>
2015-06-18 2:51 ` Hin-Tak Leung
2015-06-18 12:58 ` Sergei Antonov
2015-06-18 15:37 ` Hin-Tak Leung
2015-06-18 16:19 ` Sergei Antonov
2015-06-18 17:16 ` Hin-Tak Leung
2015-06-18 20:51 ` Sergei Antonov
2015-06-18 22:16 ` Hin-Tak Leung
2015-06-19 1:30 ` Sergei Antonov
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=1433637776-3559-1-git-send-email-saproj@gmail.com \
--to=saproj@gmail.com \
--cc=aia21@cam.ac.uk \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=htl10@users.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=slava@dubeyko.com \
--cc=sougata@tuxera.com \
--cc=viro@zeniv.linux.org.uk \
/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).