From: Hangyu Hua <hbh25y@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: balbi@kernel.org, gregkh@linuxfoundation.org, axboe@kernel.dk,
jj251510319013@gmail.com, dan.carpenter@oracle.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] usb: gadget: clear related members when goto fail
Date: Sat, 1 Jan 2022 00:15:25 +0800 [thread overview]
Message-ID: <268b05c1-846e-c229-277c-140c13fc87dc@gmail.com> (raw)
In-Reply-To: <Yc8odYb41iNuQ16J@rowland.harvard.edu>
I get that. I will fix and resubmit my patch.
Thanks again.
On 2021/12/31 下午11:57, Alan Stern wrote:
> On Fri, Dec 31, 2021 at 10:31:51AM +0800, Hangyu Hua wrote:
>> On 2021/12/31 上午3:46, Alan Stern wrote:
>
>>>> @@ -1892,7 +1895,12 @@ dev_config (struct file *fd, const char __user *buf, size_t len, loff_t *ptr)
>>>> }
>>>> return value;
>>>>
>>>> +fail2:
>>>> + dev->dev = NULL;
>>>> +fail1:
>>>> + dev->hs_config = NULL;
>>>
>>> It is not necessary to have all these different statement labels. You
>>> can simply have "fail:" clear all three pointers.
>
>> I don't think so. It is not necessary to clean all three pointers if
>> some of them aren't kbuf. I think it may be better to keep their own
>> pointers.
>
> If the pointers aren't set to a region inside kbuf then they are
> meaningless. There is no reason to keep the old values. It is better
> to avoid multiple unnecessary statement labels.
>
> Alan Stern
>
prev parent reply other threads:[~2021-12-31 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 5:11 [PATCH v3 0/2] usb: gadget: use after free in dev_config Hangyu Hua
2021-12-30 5:11 ` [PATCH v3 1/2] usb: gadget: don't release an existing dev->buf Hangyu Hua
2021-12-30 5:11 ` [PATCH v3 2/2] usb: gadget: clear related members when goto fail Hangyu Hua
2021-12-30 19:46 ` Alan Stern
2021-12-30 19:50 ` Alan Stern
2021-12-31 2:31 ` Hangyu Hua
2021-12-31 15:57 ` Alan Stern
2021-12-31 16:15 ` Hangyu Hua [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=268b05c1-846e-c229-277c-140c13fc87dc@gmail.com \
--to=hbh25y@gmail.com \
--cc=axboe@kernel.dk \
--cc=balbi@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=jj251510319013@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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