summarise aufs issues and possible patches

[Ozan Çağlayan]

hooanon05 at yahoo.co.jp wrote On 25-02-2009 07:42:
> This action item was born at the irc meeting on 24 Feb.
> 
> Current Jaunty kernel contains aufs version 20080609. It is very old
> (over half a year ago) and there are several bugfixes since then. The
> History file describes about 50 bugfixes and other enhancements from
> 20080609 till 20090126.
> I attached a list of some of them. See
> <http://aufs.sourceforge.net/History> or log messages in CVS-ed source
> files fro more detail.
> 
> Although I am not sure how ubuntu people uses aufs, I am afraid they
> will meet some of known bugs.
> 
> Latest aufs is version 2 (aufs2) which was born responding the
> discussion at last UDS. It supports linux-2.6.27 and later, but some
> features/configurations are dropped in order to make source files
> simpler and easier to be reviewed. I found the ubuntu configuration
> enables CONFIG_AUFS_{EXPORT,SHWH,STAT}. If these features are important
> for ubuntu users, you cannot switch to aufs2 yet.
> And I suspended maintaining aufs1 (which ubuntu adopts), so aufs1
> doesn't support linux-2.6.28.
> 
> Finally there are several ways we choose.
> 
> - Jaunty keeps old aufs1
>   This is the easiest way. You may want to select it until an actual
>   problem will be reported.
> 
> - I upgrade aufs1 to support 2.6.28 and Jaunty adopts it
>   Because aufs2 is very new and doesn't support
>   CONFIG_AUFS_{EXPORT,SHWH,STAT}, you may want to keep using aufs1. In
>   this case, I will modify the latest aufs1 to support 2.6.28 (or
>   later). Also I may have to follow some ubuntu specific kernel changes.
>   You can keep on using the aufs features which are curretnly enabled in
>   ubuntu kernel.
>   FYI, debian stable(5.0.0, lenny)/testing/unstable adopt aufs1
>   20080714+their patch. And debian experimental adopts aufs1
>   20081208+their patch currently.
> 
> - Jaunty adopts aufs2
>   This is my recommendation, but I can understand that you may not like
>   it. It is smaller and faster(hopefully) than aufs1 and support
>   linux-2.6.27 and later (but not yet 2.6.29-rcN).
>   In this case you cannot select CONFIG_AUFS_{EXPORT,SHWH,STAT}.
> 
> Before I start develping a patch, I need to know your choice.

I already made aufs2 compilable for 2.6.29_rcX without _EXPORT support for Pardus Linux. Here are the
patches[0] that I'm applying over the following CONFIG_AUFS_ set:

CONFIG_AUFS=m
#
#
CONFIG_AUFS_BRANCH_MAX_127=y
# CONFIG_AUFS_BRANCH_MAX_511 is not set
# CONFIG_AUFS_BRANCH_MAX_1023 is not set
# CONFIG_AUFS_BRANCH_MAX_32767 is not set
CONFIG_AUFS_STAT=y
CONFIG_AUFS_HINOTIFY=y
# CONFIG_AUFS_EXPORT is not set
# CONFIG_AUFS_ROBR is not set
# CONFIG_AUFS_DLGT is not set
CONFIG_AUFS_HIN_OR_DLGT=y
CONFIG_AUFS_SHWH=y
CONFIG_AUFS_RR_SQUASHFS=y
# CONFIG_AUFS_SEC_PERM_PATCH is not set
CONFIG_AUFS_SPLICE_PATCH=y
CONFIG_AUFS_LHASH_PATCH=y
CONFIG_AUFS_PUT_FILP_PATCH=y
CONFIG_AUFS_BR_NFS=y
CONFIG_AUFS_BR_NFS_V4=y
CONFIG_AUFS_BR_XFS=y
# CONFIG_AUFS_FSYNC_SUPER_PATCH is not set
CONFIG_AUFS_DENY_WRITE_ACCESS_PATCH=y
# CONFIG_AUFS_WORKAROUND_FUSE is not set
CONFIG_AUFS_GETATTR=y
# CONFIG_AUFS_DEBUG is not set
# CONFIG_AUFS_COMPAT is not set
# CONFIG_AUFS_UNIONFS22_PATCH is not set
# CONFIG_AUFS_UNIONFS23_PATCH is not set

[0]: http://svn.pardus.org.tr/pardus/playground/ozan/kernel/kernel-unstable/files/aufs/


Regards,

-- 
Ozan Çağlayan
http://www.pardus.org.tr/eng