From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@barebox.org>
Subject: Re: [PATCH master 1/4] commands: stat: fix leaking file descriptors on early exit
Date: Mon, 23 Jun 2025 10:36:57 +0200 [thread overview]
Message-ID: <175066781759.3604753.627511809714129880.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250623062032.3527006-1-a.fatoum@barebox.org>
On Mon, 23 Jun 2025 08:20:29 +0200, Ahmad Fatoum wrote:
> We currently leak the dirfd if we encounter an error during option
> parsing. Fix this by only recording the path at first and opening the
> dirfd once all options have been parsed.
>
>
Applied, thanks!
[1/4] commands: stat: fix leaking file descriptors on early exit
https://git.pengutronix.de/cgit/barebox/commit/?id=c7179f4d267a (link may not be stable)
[2/4] lib: idr: make idr_for_each_entry removal safe
https://git.pengutronix.de/cgit/barebox/commit/?id=4cee126abc0d (link may not be stable)
[3/4] startup: track system state with regards to initcall/exitcalls
https://git.pengutronix.de/cgit/barebox/commit/?id=18993a87a236 (link may not be stable)
[4/4] fs: do not skip fs_remove when calling umount ramfs
https://git.pengutronix.de/cgit/barebox/commit/?id=8dbe672c662b (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-06-23 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 6:20 Ahmad Fatoum
2025-06-23 6:20 ` [PATCH master 2/4] lib: idr: make idr_for_each_entry removal safe Ahmad Fatoum
2025-06-23 6:20 ` [PATCH master 3/4] startup: track system state with regards to initcall/exitcalls Ahmad Fatoum
2025-06-23 6:20 ` [PATCH master 4/4] fs: do not skip fs_remove when calling umount ramfs Ahmad Fatoum
2025-06-23 8:36 ` 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=175066781759.3604753.627511809714129880.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@barebox.org \
--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