From: Jia-Ju Bai <baijiaju1990@gmail.com>
To: Joseph Qi <joseph.qi@linux.alibaba.com>,
mark@fasheh.com, jlbec@evilplan.org
Cc: ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] fs: ocfs2: Fix possible null-pointer dereferences in ocfs2_xa_prepare_entry()
Date: Fri, 26 Jul 2019 17:50:06 +0800 [thread overview]
Message-ID: <620ac436-ffbc-8429-b952-278cd2a8aaba@gmail.com> (raw)
In-Reply-To: <b6aef7d8-9884-7349-bcec-0c8654d1b062@linux.alibaba.com>
On 2019/7/26 17:37, Joseph Qi wrote:
>
> On 19/7/26 11:36, Jia-Ju Bai wrote:
>> In ocfs2_xa_prepare_entry(), there is an if statement on line 2136 to
>> check whether loc->xl_entry is NULL:
>> if (loc->xl_entry)
>>
>> When loc->xl_entry is NULL, it is used on line 2158:
>> ocfs2_xa_add_entry(loc, name_hash);
>> loc->xl_entry->xe_name_hash = cpu_to_le32(name_hash);
>> loc->xl_entry->xe_name_offset = cpu_to_le16(loc->xl_size);
>> and line 2164:
>> ocfs2_xa_add_namevalue(loc, xi);
>> loc->xl_entry->xe_value_size = cpu_to_le64(xi->xi_value_len);
>> loc->xl_entry->xe_name_len = xi->xi_name_len;
>>
>> Thus, possible null-pointer dereferences may occur.
>>
>> To fix these bugs, if loc-xl_entry is NULL, ocfs2_xa_prepare_entry()
>> abnormally returns with -EINVAL.
>>
>> These bugs are found by a static analysis tool STCheck written by us.
>>
>> Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
>> ---
>> fs/ocfs2/xattr.c | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/ocfs2/xattr.c b/fs/ocfs2/xattr.c
>> index 385f3aaa2448..f690502daf3c 100644
>> --- a/fs/ocfs2/xattr.c
>> +++ b/fs/ocfs2/xattr.c
>> @@ -2154,8 +2154,10 @@ static int ocfs2_xa_prepare_entry(struct ocfs2_xa_loc *loc,
>> }
>> }
>> ocfs2_xa_wipe_namevalue(loc);
>> - } else
>> - ocfs2_xa_add_entry(loc, name_hash);
>> + } else {
>> + rc = -EINVAL;
>> + goto out;
>> + }
> Since entry not found, so there is nothing to do in
> ocfs2_xa_prepare_entry(). We may change it like:
>
> if (!loc->xl_entry) {
> rc = -EINVAL;
> goto out;
> }
>
> if (ocfs2_xa_can_reuse_entry(loc, xi)) {
> ......
> }
> .....
>
Okay, I will send a v2 patch.
Best wishes,
Jia-Ju Bai
prev parent reply other threads:[~2019-07-26 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 3:36 Jia-Ju Bai
2019-07-26 9:37 ` Joseph Qi
2019-07-26 9:50 ` Jia-Ju Bai [this message]
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=620ac436-ffbc-8429-b952-278cd2a8aaba@gmail.com \
--to=baijiaju1990@gmail.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@oss.oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome