From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 3/5] f2fs: fix to avoid NULL pointer dereference
Date: Wed, 25 Mar 2020 08:50:14 -0700 [thread overview]
Message-ID: <20200325155014.GB65658@google.com> (raw)
In-Reply-To: <20200325091811.60725-1-yuchao0@huawei.com>
Hi Chao,
I don't want to rebase old commit at this moment, so applied on top of the tree.
Thanks,
On 03/25, Chao Yu wrote:
> Unable to handle kernel NULL pointer dereference at virtual address 00000000
> PC is at f2fs_free_dic+0x60/0x2c8
> LR is at f2fs_decompress_pages+0x3c4/0x3e8
> f2fs_free_dic+0x60/0x2c8
> f2fs_decompress_pages+0x3c4/0x3e8
> __read_end_io+0x78/0x19c
> f2fs_post_read_work+0x6c/0x94
> process_one_work+0x210/0x48c
> worker_thread+0x2e8/0x44c
> kthread+0x110/0x120
> ret_from_fork+0x10/0x18
>
> In f2fs_free_dic(), we can not use f2fs_put_page(,1) to release dic->tpages[i],
> as the page's mapping is NULL.
>
> Signed-off-by: Chao Yu <yuchao0@huawei.com>
> ---
> v2:
> - fix to skip release tpages[i] if it is NULL in error path.
> fs/f2fs/compress.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/compress.c b/fs/f2fs/compress.c
> index ef7dd04312fe..6e10800729b6 100644
> --- a/fs/f2fs/compress.c
> +++ b/fs/f2fs/compress.c
> @@ -1137,7 +1137,10 @@ void f2fs_free_dic(struct decompress_io_ctx *dic)
> for (i = 0; i < dic->cluster_size; i++) {
> if (dic->rpages[i])
> continue;
> - f2fs_put_page(dic->tpages[i], 1);
> + if (!dic->tpages[i])
> + continue;
> + unlock_page(dic->tpages[i]);
> + put_page(dic->tpages[i]);
> }
> kfree(dic->tpages);
> }
> --
> 2.18.0.rc1
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, chao@kernel.org
Subject: Re: [PATCH v2 3/5] f2fs: fix to avoid NULL pointer dereference
Date: Wed, 25 Mar 2020 08:50:14 -0700 [thread overview]
Message-ID: <20200325155014.GB65658@google.com> (raw)
In-Reply-To: <20200325091811.60725-1-yuchao0@huawei.com>
Hi Chao,
I don't want to rebase old commit at this moment, so applied on top of the tree.
Thanks,
On 03/25, Chao Yu wrote:
> Unable to handle kernel NULL pointer dereference at virtual address 00000000
> PC is at f2fs_free_dic+0x60/0x2c8
> LR is at f2fs_decompress_pages+0x3c4/0x3e8
> f2fs_free_dic+0x60/0x2c8
> f2fs_decompress_pages+0x3c4/0x3e8
> __read_end_io+0x78/0x19c
> f2fs_post_read_work+0x6c/0x94
> process_one_work+0x210/0x48c
> worker_thread+0x2e8/0x44c
> kthread+0x110/0x120
> ret_from_fork+0x10/0x18
>
> In f2fs_free_dic(), we can not use f2fs_put_page(,1) to release dic->tpages[i],
> as the page's mapping is NULL.
>
> Signed-off-by: Chao Yu <yuchao0@huawei.com>
> ---
> v2:
> - fix to skip release tpages[i] if it is NULL in error path.
> fs/f2fs/compress.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/compress.c b/fs/f2fs/compress.c
> index ef7dd04312fe..6e10800729b6 100644
> --- a/fs/f2fs/compress.c
> +++ b/fs/f2fs/compress.c
> @@ -1137,7 +1137,10 @@ void f2fs_free_dic(struct decompress_io_ctx *dic)
> for (i = 0; i < dic->cluster_size; i++) {
> if (dic->rpages[i])
> continue;
> - f2fs_put_page(dic->tpages[i], 1);
> + if (!dic->tpages[i])
> + continue;
> + unlock_page(dic->tpages[i]);
> + put_page(dic->tpages[i]);
> }
> kfree(dic->tpages);
> }
> --
> 2.18.0.rc1
next prev parent reply other threads:[~2020-03-25 15:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 9:18 [f2fs-dev] [PATCH v2 3/5] f2fs: fix to avoid NULL pointer dereference Chao Yu
2020-03-25 9:18 ` Chao Yu
2020-03-25 15:50 ` Jaegeuk Kim [this message]
2020-03-25 15:50 ` Jaegeuk Kim
2020-03-26 9:30 ` [f2fs-dev] " Chao Yu
2020-03-26 9:30 ` Chao Yu
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=20200325155014.GB65658@google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.