From: Kari Argillander <kari.argillander@gmail.com>
To: yan <chinayanlei2002@163.com>
Cc: almaz.alexandrovich@paragon-software.com, ntfs3@lists.linux.dev,
Yan Lei <yan_lei@dahuatech.com>
Subject: Re: [PATCH] fs: ntfs3: fix Using uninitialized value n when calling indx_read
Date: Fri, 22 Apr 2022 11:51:42 +0300 [thread overview]
Message-ID: <6a5cf7da-9ff3-e0dd-19d9-63aa82e6d06a@gmail.com> (raw)
In-Reply-To: <6a8bea15.34ed.1805067b0fb.Coremail.chinayanlei2002@163.com>
Do not top post.
On 22.4.2022 11.33, yan wrote:
>
> It's not a mistake, I can't send patchs with my company's email due
> to some security issues。
Then patch cannot be accepted. If you tag patch with email which does
not work how do people message to you if needed. Also how we can know
that it is your email if you event can't use it. That company security
policy goes too far if you can't even use your email address.
> The CWE bug were detected by a static code scanning tool called
> CodeS of my company(I don't kown its real name).
> The CodeS reports:
> Use of an uninitialized variable(CWE-457)
> Using uninitialized value "n" when calling indx_read.
>
> commit messages is as below:
> This CWE bug were detected by a static code scanning tool,
> Fix using unitialized value n when calling indx_read
You need to send v2.
> At 2022-04-21 01:50:27, "Kari Argillander" <kari.argillander@gmail.com> wrote:
>>This patch is sended from address chinayanlei2002@163.com you need to
>>send it from yan_lei@dahuatech.com this was probably mistake?
>>
>>Also please write commit message. Always good to write how did you spot
>>this and what message some analyzer showed to you. This way everyone
>>else will can verify and maybe even learn to use new tools. This also
>>looks like it really fix something so this needs fix tag so it can be
>>easily back ported to stable.
>>
>>On 10.4.2022 9.09, chinayanlei2002@163.com wrote:
>>> From: Yan Lei <yan_lei@dahuatech.com>
>>>
>>> Signed-off-by: Yan Lei <yan_lei@dahuatech.com>
>>> ---
>>> fs/ntfs3/index.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/fs/ntfs3/index.c b/fs/ntfs3/index.c
>>> index 6f81e3a49..76ebea253 100644
>>> --- a/fs/ntfs3/index.c
>>> +++ b/fs/ntfs3/index.c
>>> @@ -1994,7 +1994,7 @@ static int indx_free_children(struct ntfs_index *indx, struct ntfs_inode *ni,
>>> const struct NTFS_DE *e, bool trim)
>>> {
>>> int err;
>>> - struct indx_node *n;
>>> + struct indx_node *n = NULL;
>>> struct INDEX_HDR *hdr;
>>> CLST vbn = de_get_vbn(e);
>>> size_t i;
>
>
>
next prev parent reply other threads:[~2022-04-22 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 6:09 [PATCH] fs: ntfs3: fix Using uninitialized value n when calling indx_read chinayanlei2002
2022-04-20 17:50 ` Kari Argillander
[not found] ` <6a8bea15.34ed.1805067b0fb.Coremail.chinayanlei2002@163.com>
2022-04-22 8:51 ` Kari Argillander [this message]
2022-06-09 16:26 ` Konstantin Komarov
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=6a5cf7da-9ff3-e0dd-19d9-63aa82e6d06a@gmail.com \
--to=kari.argillander@gmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=chinayanlei2002@163.com \
--cc=ntfs3@lists.linux.dev \
--cc=yan_lei@dahuatech.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