From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Marek Vasut <marex@denx.de>,
Michael Ferolito <michaelsunn101@gmail.com>,
u-boot@lists.denx.de
Cc: Heiko Schocher <hs@denx.de>, Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH v2] USB: Fix NULLPTR dereference when serial# is unset
Date: Tue, 28 Jan 2025 10:11:12 +0100 [thread overview]
Message-ID: <87wmefqp5b.fsf@baylibre.com> (raw)
In-Reply-To: <2f367a3a-659b-4fe5-be34-e270ee941866@denx.de>
Hi Michael,
Thank you for the patch.
On mar., janv. 28, 2025 at 02:49, Marek Vasut <marex@denx.de> wrote:
> On 1/28/25 1:30 AM, Michael Ferolito wrote:
>> The current behaviour of this function will dereference a null pointer
>> if the serial# environment variable is unset. This was discovered on a
>> board where U-Boot did not have access to the first 256MB of ram,
>> resulting in a board crash.
>> In the event that U-Boot has full access to memory, it will still read
>> from address 0, which is probably not optimal.
>> This simple check is enough to fix it
>>
>> Signed-off-by: Michael Ferolito <michaelsunn101@gmail.com>
>> Cc: Marek Vasut <marex@denx.de>
>> Cc: Heiko Schocher <hs@denx.de>
>> Cc: Kyungmin Park <kyungmin.park@samsung.com>
> The subject tag is "usb: gadget: g_dnl:" instead of "USB:" , with that
> fixed:
>
> Reviewed-by: Marek Vasut <marex@denx.de>
Agreed with Marek on this. Please add:
Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
As well.
Marek, since this is gadget, can this go through my tree?
In that case, Michael, I can fix up the subject when applying (to avoid
you sending a v2)
Let me know if that works.
Thanks,
Mattijs
>
> Thanks
next prev parent reply other threads:[~2025-01-28 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 0:30 [PATCH v2] USB: Fix NULLPTR dereference when serial# is unset Michael Ferolito
2025-01-28 1:49 ` Marek Vasut
2025-01-28 9:11 ` Mattijs Korpershoek [this message]
2025-01-28 9:17 ` Heiko Schocher
2025-01-28 9:39 ` Mattijs Korpershoek
2025-01-28 10:40 ` Marek Vasut
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=87wmefqp5b.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=hs@denx.de \
--cc=kyungmin.park@samsung.com \
--cc=marex@denx.de \
--cc=michaelsunn101@gmail.com \
--cc=u-boot@lists.denx.de \
/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