Building on comment #1, a few things that aren't on the bug yet:

**26.04 LTS is affected too, not just 26.10 chroots.** 26.04's own rust-
coreutils (0.10.0-1ubuntu2~26.04.1) carries the same patch and panics
the same way. That matters for the debootstrap fix proposed in #1: it
keeps `setup_proc_symlink` for every codename up to and including
`resolute`, so a 26.04 chroot built in Docker would still hit this.

**Reproducer without debootstrap**, on a stock 26.04 image:

```
docker run --rm --privileged ubuntu:26.04 bash -c '
  mkdir /c && cp -a /usr /etc /c/
  ln -s usr/bin /c/bin; ln -s usr/lib /c/lib; ln -s usr/lib64 /c/lib64
  ln -s /proc /c/proc
  chroot /c /bin/true'
```

```
thread 'main' panicked at src/bin/coreutils.rs:81:13:
Unable to read /proc/self/exe: Too many levels of symbolic links (os error 40)
```

**Ubuntu-only.** The upstream uutils 0.12.0 release binary runs `true`
and `ls` fine in the same chroot; upstream doesn't read `/proc/self/exe`
at startup, so only the Ubuntu patch panics.

**On where to fix it:** the patch already skips the check when
`/proc/self/exe` is `NotFound` (no `/proc` mounted). A `/proc` that is a
dangling or looping symlink (`ELOOP`) is the same situation, a chroot
without a usable `/proc`, but it panics instead. Skipping the check on
`ELOOP` as well would cover any chroot with a broken `/proc`
(debootstrap, other build tools, hand-made chroots) and every release
that ships the patch, including 26.04. The debootstrap change from #1
still seems worth doing so new chroots get a real `/proc`, but on its
own it leaves 26.04 and non-debootstrap chroots exposed. My account
can't add package tasks here, so could a bug triager add rust-coreutils
(Ubuntu) and debootstrap (Ubuntu)? The fix could land in either, so it
seems worth tracking both.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2166212

Title:
  Pbuilder-dist cannot create a 26.10 chroot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2166212/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to