From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH] fs: combine __d_alloc's allocations into one
Date: Fri, 14 Mar 2025 16:54:31 +0100 [thread overview]
Message-ID: <174196767114.4115826.116033472155325437.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250313064540.76961-1-a.fatoum@pengutronix.de>
On Thu, 13 Mar 2025 07:45:40 +0100, Ahmad Fatoum wrote:
> Instead of doing two allocations, one for the struct dentry and one for
> the full name, just do one allocation and place them after each other.
>
> This has the extra benefit of fixing a leak of the dentry allocation
> when the second allocation for the file name fails.
>
>
> [...]
Applied, thanks!
[1/1] fs: combine __d_alloc's allocations into one
https://git.pengutronix.de/cgit/barebox/commit/?id=9b21612c3bc0 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-03-14 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 6:45 Ahmad Fatoum
2025-03-14 15:54 ` 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=174196767114.4115826.116033472155325437.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@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