[Bug 729338] Re: yama hardlink restriction misbehaves under aufs

2011-10-12 Thread Daniel
Same problem here. Use this script to reproduce script: testuser=set-a-valid-non-root-user mkdir d1/ mkdir d1/x/ echo This is a samefile-test d1/x/file.txt chown $testuser: d1/x/ d1/x/* mksquashfs d1/ testdata_L1.squashfs -noappend mkdir L1root mount -t squashfs -oloop ./testdata_L1.squashfs

[Bug 729338] Re: yama hardlink restriction misbehaves under aufs

2011-10-12 Thread Daniel
*** This bug is a duplicate of bug 663069 *** https://bugs.launchpad.net/bugs/663069 ** This bug has been marked a duplicate of bug 663069 non-accessable symlink errors when using aufs-shaddowed read-only root filesystem -- You received this bug notification because you are a member of

[Bug 729338] Re: yama hardlink restriction misbehaves under aufs

2011-08-03 Thread Robert Collins
FWIW we see this in LXC containers when we use aufs to make ephemeral containers. An easy trigger seems to be deleting a file in the rw layer that exists in the ro layer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 729338] Re: yama hardlink restriction misbehaves under aufs

2011-05-20 Thread Andy Whitcroft
Managed to reproduce this on the Oneiric kernel, the error seems to be triggered on renaming of an object on the ro layer. ** Changed in: linux (Ubuntu) Status: New = Triaged ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Assignee: