From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Chali Anis <chalianis1@gmail.com>
Subject: Re: [PATCH] boot: don't use the nfs:// mount path after freeing it
Date: Fri, 28 Aug 2026 14:16:26 +0200 [thread overview]
Message-ID: <178791938612.424881.13552395264810216646.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260826101335.2682621-1-a.fatoum@pengutronix.de>
On Wed, 26 Aug 2026 12:13:33 +0200, Ahmad Fatoum wrote:
> We free nfspath, while there is still a dangling reference to it in
> the `name' variable:
>
> nfspath = parse_nfs_url(name);
> if (nfspath)
> name = nfspath;
> ...
> free(nfspath);
>
> [...]
Applied, thanks!
[1/1] boot: don't use the nfs:// mount path after freeing it
https://git.pengutronix.de/cgit/barebox/commit/?id=ae383ffe08ff (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-08-28 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 10:13 Ahmad Fatoum
2026-08-28 12:16 ` Sascha Hauer [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=178791938612.424881.13552395264810216646.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=chalianis1@gmail.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