Regarding bug 1243591 and aufs issue with file lifecycle

[Wojciech Kocjan]

Hi,

I have submitted a bug for Ubuntu that it does not apply the
aufs3-map.patch (the bug is here: https://bugs.launchpad.net/bugs/1243591).
Joseph Salisbury has recommended me to contact the mailing list to describe
the problem in more details.

I have originally been in contact with the aufs author and the discussion
related to the issue can be found here:

http://sourceforge.net/mailarchive/forum.php?thread_name=17716.1382529737%40jrobl&forum_name=aufs-users

The outcome of the discussion is that aufs was never fully tested without
the patch, and as an outcome of the discussion and subsequent checking,
aufs now requires applying the patch to work properly.

The patch itself can be found here:

http://sourceforge.net/p/aufs/aufs3-standalone/ci/aufs3.2/tree/aufs3-mmap.patch

I believe Ubuntu should also start applying the patch. As for what the
patch does, below is explanation (also from same thread on aufs-users):

http://sourceforge.net/mailarchive/message.php?msg_id=31535074

As for some background - I am an application developer that came across an
issue that our app does not work in Docker with Ubuntu as host OS. Docker
uses aufs and when it uses aufs from Ubuntu with kernel without the said
patch, multiple files had same inode numbers (from my understanding this
was because of invalid file lifecycle), which caused dlopen() to use
incorrect files.

Previously the patch was said to be optional, but because of that issue it
should now be applied at all times.

Do you think it is possible for Ubuntu (preferably both 12.04 LTS and
13.10) to start using a Linux kernel build with the said patch applied? Do
you see any downsides of having it applied?

-- 
Wojciech Kocjan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/kernel-team/attachments/20131104/e901806d/attachment.html>