This bug was nominated against a series that is no longer supported, ie
raring. The bug task representing the raring nomination is being closed
as Won't Fix.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu Raring)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1098378
Title:
chroot+overlayfs seems to cause umount mis-behavior
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux” source package in Raring:
Won't Fix
Bug description:
If you mount an overlayfs under a loopback fs, chroot into it and
mount something, then the loopback device cannot be released. In
quantal it could, but in raring it hangs. I will attach a script
which triggers the bug (in raring).
It doesn't happen with aufs; it doesn't happen if you mount without
chrooting or pivot-rooting; it doesn't happen if you chroot but don't
do any mounting.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1098378/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
