[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#841026: marked as done (Pull: "userns: proc and sysfs mount fix")

Your message dated Sat, 15 May 2021 02:29:07 -0700 (PDT)
with message-id <609f9463.1c69fb81.cf806.5c52@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #841026,
regarding Pull: "userns: proc and sysfs mount fix"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
841026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841026
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-3.16.0-4-amd64
Version: 3.16.7-ckt17-1

The upload to jessie of linux 3.16.7-ckt17-1 included the following
change:

  - mnt: Refactor the logic for mounting sysfs and proc in a user
    namespace [1]

This broke mounting sysfs and procfs under a user namespace. There is a
fix at [2] that claims to solve the problem.

It would be great if this fix could be included in the next upload to
jessie.

Sadly, I haven't had time to run on my machine a kernel that includes
that fix. I do know, however, that the problem is still present in
3.16.36-1+deb8u1.

Thanks for considering,

-d

[1]: Original commit (I believe): https://patchwork.kernel.org/patch/6408681/
[2]: Fix: https://lists.linuxfoundation.org/pipermail/containers/2015-May/035874.html

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: