From: 白浩文 <baihaowen@meizu.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "vireshk@kernel.org" <vireshk@kernel.org>,
"johan@kernel.org" <johan@kernel.org>,
"elder@kernel.org" <elder@kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 答复: [PATCH] staging: greybus: Fix potential NULL dereference
Date: Fri, 11 Mar 2022 08:50:49 +0000 [thread overview]
Message-ID: <0a6d02d1b6374cf0bddd0f4e7fbc475a@meizu.com> (raw)
In-Reply-To: <20220311084019.w45kfluiamgosivu@vireshk-i7>
Oh, my careless to check code. Thank you for your kindly reminder.
________________________________________
发件人: Viresh Kumar <viresh.kumar@linaro.org>
发送时间: 2022年3月11日 16:40:19
收件人: 白浩文
抄送: vireshk@kernel.org; johan@kernel.org; elder@kernel.org; gregkh@linuxfoundation.org; linux-staging@lists.linux.dev; linux-kernel@vger.kernel.org
主题: Re: [PATCH] staging: greybus: Fix potential NULL dereference
On 11-03-22, 16:35, Haowen Bai wrote:
> Fix following coccicheck warning:
> drivers/staging/greybus/bootrom.c:301:35-39: ERROR: fw is NULL but dereferenced.
>
> When goto queue_work but dereference Uninitialized fw will trigger a NULL
> dereference.
Please have a look at earlier attempts like this:
https://lore.kernel.org/all/2015099.xVv48VzNit@linux.local/
--
viresh
next prev parent reply other threads:[~2022-03-11 8:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 8:35 [PATCH] staging: greybus: Fix potential NULL dereference Haowen Bai
2022-03-11 8:40 ` Viresh Kumar
2022-03-11 8:50 ` 白浩文 [this message]
2022-03-11 11:32 ` Dan Carpenter
2022-03-14 1:12 ` 答复: " 白浩文
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=0a6d02d1b6374cf0bddd0f4e7fbc475a@meizu.com \
--to=baihaowen@meizu.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@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