From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH 0/6] fs: ubootvarfs: harden parser
Date: Thu, 15 Oct 2026 10:24:18 +0200 [thread overview]
Message-ID: <179205265853.1371753.8116687204161819504.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20261002114253.2906535-1-a.fatoum@pengutronix.de>
On Fri, 02 Oct 2026 13:40:03 +0200, Ahmad Fatoum wrote:
> Fix a number of issues in our U-Boot env support, mostly unearthed by
> fuzzing with some LLM assistance.
>
> Ahmad Fatoum (6):
> fs: skip directory entries whose name does not fit struct dirent
> fs: reject negative lengths in ftruncate()
> fs: ubootvarfs: range-check the new size in truncate
> fs: ubootvarfs: do not form pointers past the end of the environment
> fs: ubootvarfs: reject variable names containing '='
> fs: ubootvarfs: handle removal of variables that are still open
>
> [...]
Applied, thanks!
[1/6] fs: skip directory entries whose name does not fit struct dirent
https://git.pengutronix.de/cgit/barebox/commit/?id=e0f9224055fa (link may not be stable)
[2/6] fs: reject negative lengths in ftruncate()
https://git.pengutronix.de/cgit/barebox/commit/?id=69481b108050 (link may not be stable)
[3/6] fs: ubootvarfs: range-check the new size in truncate
https://git.pengutronix.de/cgit/barebox/commit/?id=23c4e760fa04 (link may not be stable)
[4/6] fs: ubootvarfs: do not form pointers past the end of the environment
https://git.pengutronix.de/cgit/barebox/commit/?id=dc811b55bb47 (link may not be stable)
[5/6] fs: ubootvarfs: reject variable names containing '='
https://git.pengutronix.de/cgit/barebox/commit/?id=ce79a7e7c3be (link may not be stable)
[6/6] fs: ubootvarfs: handle removal of variables that are still open
https://git.pengutronix.de/cgit/barebox/commit/?id=7b42e5e3eb32 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-10-15 8:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 11:40 Ahmad Fatoum
2026-10-02 11:40 ` [PATCH 1/6] fs: skip directory entries whose name does not fit struct dirent Ahmad Fatoum
2026-10-02 11:40 ` [PATCH 2/6] fs: reject negative lengths in ftruncate() Ahmad Fatoum
2026-10-02 11:40 ` [PATCH 3/6] fs: ubootvarfs: range-check the new size in truncate Ahmad Fatoum
2026-10-02 11:40 ` [PATCH 4/6] fs: ubootvarfs: do not form pointers past the end of the environment Ahmad Fatoum
2026-10-02 11:40 ` [PATCH 5/6] fs: ubootvarfs: reject variable names containing '=' Ahmad Fatoum
2026-10-02 11:40 ` [PATCH 6/6] fs: ubootvarfs: handle removal of variables that are still open Ahmad Fatoum
2026-10-15 8:24 ` 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=179205265853.1371753.8116687204161819504.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