The boot process can't delete old /tmp when it contains non-UTF-8 file names

  • Open
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • Maxime Devos
Owner
unassigned
Submitted by
Maxime Devos
Severity
important

Debbugs page

M
M
Maxime Devos wrote on 24 Sep 2022 14:12
(name . bug-guix)(address . bug-guix@gnu.org)
ba338848-715e-d6fb-0c68-40904c8077b6@telenet.be
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.
Greetings,
Maxime.
Attachment: OpenPGP_signature
M
M
Maxime Devos wrote on 25 Sep 2022 04:25
(address . 58048@debbugs.gnu.org)
00fa5db7-9991-f894-c757-2557e3ac8f9d@telenet.be
On 24-09-2022 23:12, Maxime Devos wrote:
Toggle quote (2 lines)
> 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"
I didn't see the warning this time though.
Greetings,
Maxime.
Attachment: OpenPGP_signature
L
L
Ludovic Courtès wrote on 26 Sep 2022 08:48
Re: bug#58048: The boot process can't delete old /tmp when it contains non-UTF-8 file names
(name . Maxime Devos)(address . maximedevos@telenet.be)(address . 58048@debbugs.gnu.org)
874jwukugb.fsf@gnu.org
Maxime Devos <maximedevos@telenet.be> skribis:

Toggle quote (10 lines)
> 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?

Ludo’.
L
L
Ludovic Courtès wrote on 26 Sep 2022 08:49
control message for bug #58048
(address . control@debbugs.gnu.org)
8735cekufk.fsf@gnu.org
severity 58048 important
quit
M
M
Maxime Devos wrote on 27 Sep 2022 04:12
Re: bug#58048: The boot process can't delete old /tmp when it contains non-UTF-8 file names
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 58048@debbugs.gnu.org)
05423c96-7954-fe49-ae08-b35c29d7c5b3@telenet.be
On 26-09-2022 17:48, Ludovic Courtès wrote:
Toggle quote (21 lines)
> 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: OpenPGP_signature
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 58048@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 58048
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch