From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 58048@debbugs.gnu.org
Subject: bug#58048: The boot process can't delete old /tmp when it contains non-UTF-8 file names
Date: Tue, 27 Sep 2022 13:12:19 +0200 [thread overview]
Message-ID: <05423c96-7954-fe49-ae08-b35c29d7c5b3@telenet.be> (raw)
In-Reply-To: <874jwukugb.fsf@gnu.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 996 bytes --]
On 26-09-2022 17:48, Ludovic Courtès wrote:
> Maxime Devos <maximedevos@telenet.be> skribis:
>
>> On 24-09-2022 23:12, Maxime Devos wrote:
>>> Will try to catch the exact warning message and write a reproducer
>>> at the next boot, for now I write it here before I forget about it.
>>
>> Two reproducers:
>>
>> (1) Compile ripgrep and somehow let it fail (but after it creates
>> non-UTF-8 file names), reboot, "ls /tmp"
>> (2) Run touch /tmp/OOPS-$(echo -e '\xff')-OOPS, reboot, "ls /tmp"
>
> The culprit would be ‘cleanup-gexp’ in (gnu services). It keeps going
> upon ‘system-error’ (like ENOENT), but it could be that you’re getting
> ‘encoding-error’ in this case.
>
> In that case, ‘fail-safe’ should also catch this.
>
> We can extend ‘%test-cleanup’ in (gnu tests base) to exercise this.
>
> Would you like to give it a spin?
Yes, just not yet (low priority, doesn't block the boot, just a bit
annoying).
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2022-09-27 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 21:12 bug#58048: The boot process can't delete old /tmp when it contains non-UTF-8 file names Maxime Devos
2022-09-25 11:25 ` Maxime Devos
2022-09-26 15:48 ` Ludovic Courtès
2022-09-27 11:12 ` Maxime Devos [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=05423c96-7954-fe49-ae08-b35c29d7c5b3@telenet.be \
--to=maximedevos@telenet.be \
--cc=58048@debbugs.gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.