From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: v2025.06.1
Date: Wed, 25 Jun 2025 10:54:59 +0200 [thread overview]
Message-ID: <aFu5Y1-1w7z4AbA7@pengutronix.de> (raw)
Hi All,
I just released v2025.06.1.
v2025.06.0 contains an annoying bug which requires a stable update.
v2025.06.0 won't let you create a file in filesystems supported by the
legacy FS layer, most prominently used by the FAT filesystem. This is
easy to reproduce by issuing a "echo -o /vfat/foo bar" when /vfat is
contains a mounted FAT. This also breaks saving the environment on
systems which store the environment on FAT partitions like the TI
Omap/AMxxx and Raspberry Pi platforms.
If you are affected by this bug please update to v2025.06.1.
See https://lore.kernel.org/barebox/20250624152148.2230298-1-a.fatoum@pengutronix.de/T/#u
for the patch and background of the issue.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
reply other threads:[~2025-06-25 9:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aFu5Y1-1w7z4AbA7@pengutronix.de \
--to=s.hauer@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