apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634729/+files/acpidump.txt
--
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/19
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634728/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634727/+files/UdevDb.txt
--
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/1998602
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634726/+files/RfKill.txt
--
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/1998602
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634725/+files/PulseList.txt
--
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/
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634724/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634723/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634722/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634721/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634720/+files/PaInfo.txt
--
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/1998602
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634719/+files/Lsusb-v.txt
--
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/1998
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634717/+files/Lsusb.txt
--
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/1998602
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634718/+files/Lsusb-t.txt
--
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/1998
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634716/+files/Lspci-vt.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, whic
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634714/+files/IwConfig.txt
--
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/19
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634715/+files/Lspci.txt
--
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/1998602
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634712/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "HookError_ubuntu.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634713/+files/HookError_ubuntu.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1998602/+attachment/5634711/+files/CRDA.txt
--
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/1998602
Ti
apport information
** Tags added: apport-collected jammy
** Description changed:
This was reported (and worked around) in https://github.com/project-
stacker/stacker/pull/333.
The kernel does not allow user.* xattrs on a symlink. However, on
5.15.0-53-generic and 5.19.0-21-generic, b
> Fwiw, I think you need index=on enabled for origin xattrs to be set.
Did try that, no difference. Anyway I probably just need to take a
closer look at what exact operations are done under /etc/rc*.d when
disabling a service... I'm sure I'm missing something obvious.
--
You received this bug n
Public bug reported:
This was reported (and worked around) in https://github.com/project-
stacker/stacker/pull/333.
The kernel does not allow user.* xattrs on a symlink. However, on
5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu mainline
build (6.1.0-060100rc5-generic), an unpriv
*** This bug is a duplicate of bug 1628336 ***
https://bugs.launchpad.net/bugs/1628336
** This bug has been marked a duplicate of bug 1628336
mount-image-callback cannot mount partitioned disk image
--
You received this bug notification because you are a member of Kernel
Packages, which i
Well, actually on virtualbox it's touch-and-go.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1728109
Title:
nbd (
http://pastebin.com/raw/YPGG6usG is the reproduction script.
In virtualbox it actually passes. Maybe this really is a problem with
the disk driver for vmware?
** Description changed:
I've been trying this on several platforms -
16.04 physical host
16.04 VMware
17.04 vmware
The
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998191/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998194/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998193/+files/UdevDb.txt
--
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/1728109
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998192/+files/PulseList.txt
--
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/
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998186/+files/Lsusb.txt
--
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/1728109
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998188/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998190/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998187/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998189/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998185/+files/Lspci.txt
--
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/1728109
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998184/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998183/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1728109/+attachment/4998182/+files/CRDA.txt
--
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/1728109
Ti
apport information
** Tags added: apport-collected zesty
** Description changed:
I've been trying this on several platforms -
16.04 physical host
16.04 VMware
17.04 vmware
The script pasted below creates a virtual disk, writes a partition
table, creates an fs and some thin pool
Public bug reported:
I've been trying this on several platforms -
16.04 physical host
16.04 VMware
17.04 vmware
The script pasted below creates a virtual disk, writes a partition
table, creates an fs and some thin pools, then verifies that writes
happened as expected.
On 16.04 physical host it
I've seen reports that this is fixed in 4.10?
--
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/882147
Title:
overlayfs does not implement inotify interfaces correctly
Status in coreutils
Nope, tail -f is still broken at least in 4.12.
--
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/882147
Title:
overlayfs does not implement inotify interfaces correctly
Status in coreutil
Just re-tested. The z kernel builds fine. the yakkety-proposed kernel
still fails to build:
cc1: fatal error:
/home/ubuntu/linux-4.8.0/ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h:
No such file or directory
compilation terminated.
--
You received this bug notification because you a
** Tags added: bot-stop-nagging
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1641168
Title:
packaging error in yak
Public bug reported:
When I try to build the kernel source from yakkety-updates locally, I
get failure like:
cc1: fatal error:
/home/ubuntu/linux-4.8.0/ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h:
No such file or directory
** Affects: linux (Ubuntu)
Importance: Undecided
Ass
Please open a new bug - thanks.
--
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/1448269
Title:
qemu guest hangs on nested kvm startup with host kernel oops
Status in linux package in Ubu
Thanks for the info.
If updating kernels fixes it, then it's possible, but unlikely, that it
can be fixed in userspace. Marking this as affecting the kernel.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a memb
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1602443
Title:
Bad page state in qemu-system-x86 process
Statu
How do you figure verification needed? See comment #3.
** Tags removed: verification-needed-xenial
--
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/1584163
Title:
cgroup namespace update
I recommend opening new bugs against libvirt and docker. Libvirt moves
VMS into a cpuset by default. I assume docker does the same. (My
xenial laptop runs upstart, so this is not systemd's doing)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
"LXC cases, like docker and KVM" - did you mean non-lxc cases?
xenial by default should now be using libpam-cgfs, should not be using
cgmanager, and should not be creating cpusets.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
With xenial kernel:
132 125 0:57 /lxc/x1 /sys/fs/cgroup/blkio
rw,nosuid,nodev,noexec,relatime - cgroup cgroup rw,blkio,nsroot=/lxc/x1
with xenial-proposed kernel:
134 125 0:59 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime -
cgroup cgroup rw,blkio
** Tags removed: verification-needed-x
Public bug reported:
During xenial cycle we applied a patch (and a followon fix for criu)
to fix a usability problem with cgroup namespaces and /proc/self/mountinfo.
Since then, the approach to fix it upstream has changed. Please revert
the two nsroot patches currently in xenial and yakkety, and
** Changed in: lxc (Ubuntu Xenial)
Status: Confirmed => Invalid
** No longer affects: lxc (Ubuntu Vivid)
** No longer affects: lxc (Ubuntu Wily)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
Thanks for reporting this bug. The 'kvm' package shouldn't really
exist. The bug you're referring to is in the kernel kvm code, so I'm
marking it as affecting the kernel. (If it were in the userspace qemu
package, then the 'qemu' package would be the right bug target).
** Package changed: kvm (
Thanks for reporting this bug. The 'kvm' package shouldn't really exist.
The bug you're referring to is in the kernel kvm code, so I'm marking it
as affecting the kernel. (If it were in the userspace qemu package, then
the 'qemu' package would be the right bug target).
** Package changed: kvm (Ubu
@leftyfb - what exactly is IBM asking to verify? Whether kvm works
under powervm? Did smoser's info help?
--
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/1563887
Title:
qemu-system-ppc6
Ok so if I'm following this right there are two issues:
1. the bug reporter is using a powervm partition. KVM cannot be used
there. This is not a KVM bug.
2. the xenial cloud images have an outdated 4.2 kernel which doesn't
boot in kvm on powernv. A workaround is to use the isos which do boot.
If you can reproduce this with the ppc64 xenial iso or a rootfs
installed from that, using 4.4 kernel, please let us know. Otherwise,
I think the fix will be for cloud images to be updated with a 4.4 kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which
4.4.0-16 also works.
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
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/1563887
Title:
qemu-system-ppc64
Actually the clou dimages have a 4.2 kernel. When I use a xenial beta2
iso which has 4.4.0-15-generic #31, it boots fine. I can install, and I
can boot the installed image (with same kernel) just fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Result of doing qemu-system-ppc64 -m 1024 -vnc :1 -net nic -net
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries
-drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive
file=my-seed.img,if=virtio
** Attachment added: "crash.png"
https://bugs.launchpad.ne
Hm - I can boot a wily cloud image, just not a xenial one.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1558897
Title:
guest vm hangs
Status in linux package in Ubunt
Sorry, I had forgotten my own workaround for this.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: lxc (Ubuntu)
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu)
Status: Won't Fix => Invalid
--
You received this bug notification beca
Ok, this is happening because lxc, for privileged containers, bind-
mounts /proc/sys and /proc/sys/net onto themselves. This prevents later
unprivileged mounting of /proc.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
Sorry, testcase in #8 is invalid, bc lxc-usernsexec doesn't create a new
pid namespace, so mount is denied because we do not own our
pidns->userns.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
Simplest way to reproduce:
sudo systemctl stop proc-sys-fs-binfmt_misc.automount # (just to be sure)
unshare -mpf
mount --make-rslave /
mount -t proc proc /proc
lxc-usernsexec
# mount -t proc proc /proc # permission denied, regardless what -o options may
pass.
--
You received this bug notificat
Current wily kernel is giving me the same behavior.
--
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/1543367
Title:
nested unprileged container fails to start at mounting /proc
Status in
Upstream kernel still fails:
lxc-start 20160304193125.498 ERRORlxc_conf -
conf.c:lxc_mount_auto_mounts:742 - Operation not permitted - error mounting
proc on /usr/lib/x86_64-linux-gnu/lxc/proc flags 14
lxc-start: conf.c: lxc_mount_auto_mounts: 742 Operation not permitted - error
mount
Note - I am not actively looking at this bug as I've not managed to
reproduce it. Hopefully the kernel team has it under control, please
shout if I'm needed.
If using juju first is a prerequisite to reproducing this, I can try
that, but my impression from previous reports has been that this is no
@sforshee,
Because in the past mountall would fail if we didn't.
--
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/1551854
Title:
LXD bootstrap issues on xenial
Status in linux package in
@sforshee - are you saying that removing the debugfs line from
/usr/share/lxc/config/ubuntu-common.conf fixes this for you?
--
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/1551854
Title:
Also cannot reproduce in a clean VM, so I have to assume juju is
tweaking something.
Can you show output of 'lxc config show ' where
is the container which fails?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
marking confirmed because two people have reported it, but I cannot
reproduce it yet.
--
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/1551854
Title:
LXD bootstrap issues on xenial
Statu
I'm on the same kernel
Linux sl 4.4.0-8-generic #23-Ubuntu SMP Wed Feb 24 20:45:30 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
and also have the tracefs mounted
0 ✓ serge@sl ~ $ grep debug /proc/self/mountinfo
74 19 0:7 / /sys/kernel/debug rw,relatime shared:26 - debugfs debugfs rw
44 74 0:9 / /sys/
Well, that's wily-proposed, so +1
** Tags removed: verification-needed-wily
** Tags added: verification-done
--
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/1539349
Title:
sleep from inv
Wait, that's not a valid test is it.
--
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/1539349
Title:
sleep from invalid context in aa_move_mount
Status in linux package in Ubuntu:
Fix R
I get no warnings with 4.2.0-29-generic #34-Ubuntu
--
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/1539349
Title:
sleep from invalid context in aa_move_mount
Status in linux package in
Public bug reported:
Cgroup namespaces are a new kernel feature which allows virtualizing a
container's /proc/self/cgroups and the root of future cgroupfs mounts,
to make the container appear as though it is in the / cgroup. This is
one of the pieces needed to be able to run, for instance, docker
** Changed in: qemu (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: qemu (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-meta-lts-vivid (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
It's not something I regularly do, as I normally nest inside unprivileged
lxd containers. So I can't say whether it is a regression. I did revert
to an older trusty kernel and have the same behavior.
I'm going to need to write a script to make this more easily reproducible,
but I won't have time
Note that an unprivileged user on the host is able to do these mounts.
Unprivileged users inside a privileged container cannot.
--
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/1543367
Titl
Public bug reported:
Create a trusty or xenial host. Probably use ubuntu-lxc/daily ppa to
work around other bugs.
Create a privileged container (again either trusty or xenial will do),
and install ubuntu-lxc/daily ppa there.
Create an unprivileged container in that container. It will fail at
m
I'm quite certain this is not an apparmor issue, since leaving
everything unconfined does not help.
It could be something we're doing wrong in lxc, but I'm not sure what.
It could be something inherent in mounting onto an open fd.
--
You received this bug notification because you are a member o
Public bug reported:
In xenial master-next, when I cp /bin/mount /home/ubuntu/mount, define
the following policy:
#include
/home/ubuntu/mount {
#include
#include
capability,
network,
mount,
/** mkrwixr,
}
And then run the following script under sudo from ~/ubuntu:
#!/bin/sh
app
** Changed in: cgmanager (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Pa
marking as affecting kernel given the description.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1536280
Titl
> Something I'm still not sure about is what would happen if you made a
> symlink, bind mount, etc. in upperdir with the same name as an unrelated
> file in lowerdir. This is worth checking out.
just tried a symlink and it didn't seem to affect the host directory
(/opt/cisco) which was symlinked t
Does it require the workdir to be empty?
I.e. is there a way (symlink, bind mount, something else) that a user
could use a dir they own which has a child which they don't own?
It looks like no, since
root@w1:/tmp# mount -t overlay -o lowerdir=lower,upperdir=upper,workdir=workdir
overlay /mnt
ro
in ovl_clear_empty(), the opaque bit is set on the dir in workingdir
in ovl_create_over_whiteout() (the case we're currently looking at) it is
also being set in the working dir.
in ovl_rename2(), it is set in two places, on the upper dentries for
both the old and new.
So it is never set on the l
Quoting Seth Forshee (seth.forshee...@canonical.com):
> I don't know why #2 is that much grosser than what's there now. It's
I didn't mean gross as in eeuw, I meant not fine-grained enough.
Because the capability will apply to inode permissions checks,
and we only want it to be used for the check
hat may not be ok for the ovl_rename2 case.
What we want is for inode permissions to be checked, but only the
bit in xattr_permission() checking for trusted.* to accept ns_capable.
We could special-case that in xattr_permission(), but that's not
particularly nice.
--
You received this bug notif
#2 is probably a bit too gross - we really only need the cap for the setting
of the OVL_XATTR_OPAQUE xattr in ovl_set_opaque. So we could simply override
creds again there.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Ok, I see. At one point we had a special case to allow the overlay code
to write trusted.* xattrs for creating whiteouts.
However that is gone. Therefore when overlayfs v1 (mount -t overlayfs)
is mounted, root in a user namespace also is not able to rm a file which
exists in the lower fs.
Some
The type of the underlaying file does not matter, only the type of the
replacing object.
So if you
touch $t/dev; rm $t/dev; touch $t/dev
mkdir $t/dev; rmdir $t/ev; touch $t/dev
those succeed, while
touch $t/dev; rm $t/dev; mkdir $t/dev
mkdir $t/dev; rm $t/dev; mkdir $t/dev
both fail.
--
You
In ovl_create_over_whiteout(), the ovl_set_opaque() in the S_ISDIR()
block failed.
--
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/1531747
Title:
overlay: mkdir fails if directory exists
Quoting Joseph Salisbury (joseph.salisb...@canonical.com):
> Can you see if this bug also happens with the latest mainline kernel? It can
> be downloaded from:
That is not an option, because the mainline kernel doesn't support unprivileged
overlayfs mounting which is where this happens.
--
You
summary overlay: mkdir in user namespace fails if directory exists in
lowerdir"
** Description changed:
If a directory exists in the lowerdir but not in the mounted
overlay, then mkdir of the directory in the target dir results
in a mysterious -EPERM. I've seen this both in wily kernel
Quoting Shimin (shi...@databricks.com):
> Thanks for looking into it. Are there any downsides to disabling udev in
> the container (by removing /etc/init/udev.conf for example) if we don't
> need the container to be notified of new devices?
hi, no this should have no downsides. You can just
echo
1 - 100 of 300 matches
Mail list logo
