mythbuntu-bugs team mailing list archive

[Andy Whitcroft <apw@xxxxxxxxxxxxx>]

This was fixed by this commit:

    UBUNTU: ubuntu: Yama: if an underlying filesystem provides a permissions op 
    
    When we are checking permissions on hardlinks we use generic_permissions()
    to work out if the user actually has read/write permissions and only
    then allow the link.  However where the underlying filesystem supplies
    a permissions() op there is no guarentee that the inode ownership is
    actually valid and we must use that op instead.
    
    Add a new function mirroring the core fragment from inode_permission
    using the filesystem specific permissions() op falling back to
    generic_permissions() when it is not present.
    
    With this in place links in overlayfs behave as expected.
    
    Signed-off-by: Andy Whitcroft <apw@xxxxxxxxxxxxx>


** Changed in: linux (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to a duplicate bug report (729338).
https://bugs.launchpad.net/bugs/663069

Title:
  "non-accessable symlink" errors when using aufs-shaddowed read-only
  root filesystem

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  When I updated my pxeboot/nfs system to 10.10, several applets failed to load, and the log files contained the following messages:
  Oct 19 22:25:58 computer08 kernel: [   66.326808] non-accessible hardlink creation was attempted by: gconfd-2 (fsuid 1000)
  Oct 19 22:26:05 computer08 kernel: [   73.491138] non-accessible hardlink creation was attempted by: gconfd-2 (fsuid 114)
  Oct 19 22:26:05 computer08 kernel: [   73.580608] non-accessible hardlink creation was attempted by: gdm-session-wor (fsuid 1000)
  Oct 19 22:26:09 computer08 kernel: [   77.545565] non-accessible hardlink creation was attempted by: indicator-apple (fsuid 1000)
  Oct 19 22:26:09 computer08 kernel: [   77.670861] non-accessible hardlink creation was attempted by: indicator-apple (fsuid 1000)

  Setting kernel.yama.protected_nonaccess_hardlinks=0 allows everything
  to work.

  The read-only root is configured according to the instructions at
  http://www.logicsupply.com/blog/2009/01/27/how-to-build-a-read-only-
  linux-system . It uses a initramfs script to create a tmpfs, move /,
  and mount the aufs union filesystem on / early in the boot process.

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