From: Johannes Zink <j.zink@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: [Bug] Nullpointer Exception in of_diff
Date: Tue, 13 Jun 2023 13:42:46 +0200 [thread overview]
Message-ID: <a05ed3bf-6234-5b22-11ad-c82db0c1cd14@pengutronix.de> (raw)
In-Reply-To: <044fee32-5560-2e85-a0d3-cc7cea71ed48@pengutronix.de>
Hi Ahmad,
On 6/12/23 16:50, Ahmad Fatoum wrote:
> Hello Johannes,
>
> On 12.06.23 16:26, Johannes Zink wrote:
>> Hi,
>>
>> I observed a Nullpointer Exception in barebox barebox 2023.05.0 on a Rock3a when calling
>>
>> of_diff . .
>
> This should be already fixed in next. You can ask Sascha to pick
> "commands: of_diff: simplify error handling" to master if that
> fixes your issue.
thanks for your reply, it is fixed in next indeed. I just gave it a quick test run.
@Sascha: as this fixes a Nullpointer dereference, maybe Ahmad's patch is a
candidate to pick into master?
>
> [snip]
>
> You can pipe barebox crash logs into Linux scripts/decode_stacktrace.sh
> to get line numbers (don't forget to set ARCH/CROSS_COMPILE).
> Enabling CONFIG_KASAN=y can also be very useful to pinpoint the origin
> of memory corruptions.
>
That's good to know, thank you. This will definitely help me the next time.
Johannes
> Cheers,
> Ahmad
>
>>
>> Best regards
>> Johannes
>>
>>
>
--
Pengutronix e.K. | Johannes Zink |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686| Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2023-06-13 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 14:26 Johannes Zink
2023-06-12 14:50 ` Ahmad Fatoum
2023-06-13 11:42 ` Johannes Zink [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=a05ed3bf-6234-5b22-11ad-c82db0c1cd14@pengutronix.de \
--to=j.zink@pengutronix.de \
--cc=barebox@lists.infradead.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