From: Chao Yu <yuchao0@huawei.com>
To: Jia-Ju Bai <baijiaju1990@gmail.com>, <jaegeuk@kernel.org>
Cc: <linux-f2fs-devel@lists.sourceforge.net>, <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] fs: f2fs: Possible null-pointer dereferences in update_general_status()
Date: Fri, 26 Jul 2019 11:19:41 +0800 [thread overview]
Message-ID: <2d66cd56-eccf-9086-c5db-118acce717a6@huawei.com> (raw)
In-Reply-To: <f577be2f-fc2f-9ef8-2c6c-9c247123b1ad@gmail.com>
Hi Jiaju,
Thanks for the report, I checked the code, and found it doesn't need to check
SM_I(sbi) pointer, this is because in fill_super() and put_super(), we will call
f2fs_destroy_stats() in prior to f2fs_destroy_segment_manager(), so if current
sbi can still be visited in global stat list, SM_I(sbi) should be released yet.
So anyway, let's remove unneeded check in line 70/78. :)
Thanks,
On 2019/7/25 17:49, Jia-Ju Bai wrote:
> In update_general_status(), there are two if statements to
> check whether SM_I(sbi) is NULL:
> LINE 70: if (SM_I(sbi) && SM_I(sbi)->fcc_info)
> LINE 78: if (SM_I(sbi) && SM_I(sbi)->dcc_info)
>
> When SM_I(sbi) is NULL, it is used at some places, such as:
> LINE 88: reserved_segments(sbi)
> return SM_I(sbi)->reserved_segments;
> LINE 89: overprovision_segments(sbi)
> return SM_I(sbi)->ovp_segments;
> LINE 112: MAIN_SEGS(sbi)
> (SM_I(sbi)->main_segments)
>
> Thus, possible null-pointer dereferences may occur.
>
> These bugs are found by a static analysis tool STCheck written by us.
>
> I do not know how to correctly fix these bugs, so I only report them.
>
>
> Best wishes,
> Jia-Ju Bai
> .
>
next prev parent reply other threads:[~2019-07-26 3:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 9:49 Jia-Ju Bai
2019-07-26 3:19 ` Chao Yu [this message]
2019-07-26 3:39 ` Jia-Ju Bai
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=2d66cd56-eccf-9086-c5db-118acce717a6@huawei.com \
--to=yuchao0@huawei.com \
--cc=baijiaju1990@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®