aufs3 GIT release

2013-11-03 Thread sfjro

o bugfix
- the new external patch for mmap is always required, reported by
  Wojciech Kocjan.
- describe two aufs_type.h files, reported by Ed W.

o news
- aufs3-proc_map.patch is replaced by aufs3-mmap.patch.
  The purpose of the patch is unchanged. While aufs3-proc_map.patch was
  described as optional, aufs3-mmap.patch is always required.
  And CONFIG_AUFS_PROC_MAP is removed.
  To apply the patch is the bugfix which is reported by Wojciech Kocjan.
  Additionally the patch is refined a little other than its name.


J. R. Okajima

--
- aufs3-linux.git#aufs3.2 branch
  aufs: update the donator list
  aufs: mmap, refine by inlined funcs 1/4
  aufs: mmap, refine by inlined funcs 2/4
  aufs: mmap, refine by inlined funcs (debug) 3/4
  aufs: mmap, more maintain vm_prfile 4/4
  aufs: bugfix, the external patch for mmap is always required

- aufs3-linux.git#aufs3.2.x branch
  Addition to above,
  aufs: for linux-3.2.x, mmap, more maintain vm_prfile

- aufs3-linux.git#aufs3.4 branch
  equivalent to aufs3.2

- aufs3-linux.git#aufs3.8..aufs3.x-rcN branch
  Addition to above,
  aufs: bugfix, describe two aufs_type.h files
  aufs: remove obsolete include/linux/aufs_type.h
  aufs: for linux-3.6, mmap, more maintain vm_prfile
  aufs: for linux-3.7, mmap, more maintain vm_prfile
  aufs: mmap, restore a missing vm_prfile maintainance

- aufs3-standalone.git#aufs3.2..aufs3.4 branch
  aufs: update the donator list
  aufs: bugfix, the external patch for mmap is always required
  aufs module: CONFIG_AUFS_PROC_MAP is removed
  aufs standalone: CONFIG_AUFS_PROC_MAP is removed

- aufs3-standalone.git#aufs3.8..aufs3.x-rcN branch
  Addition to above,
  aufs: bugfix, describe two aufs_type.h files
  aufs: remove obsolete include/linux/aufs_type.h

- aufs-util.git
  nothing

--
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk


Re: aufs aufs_migratepage:666: This operation is not supported

2013-11-03 Thread sfjro

Hello Flavio,

The migratepage problem is still in my head.
And I am afraid it might be related to CONFIG_AUFS_PROC_MAP.
Reading
http://download.opensuse.org/repositories/home:/flavio_castelli:/docker/openSUSE_12.3/src/
again, I've found that
- you might apply aufs3-proc_map.patch
- but you might not enable CONFIG_AUFS_PROC_MAP

If so, new aufs3-mmap.patch may solve the problem. Since without
aufs3-proc_map.patch and CONFIG_AUFS_PROC_MAP, any problem can happen
after specific operation around mmap(2).

If you are still interested in aufs and have enough time, please try
latest aufs3 release and let me know the result.

Thanks in advance
J. R. Okajima

--
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk


Re: aufs3.12 will kill aufs3.{2,2.x,4} (Re: aufs3 GIT release)

2013-11-03 Thread sfjro

sf...@users.sourceforge.net:
 In a few months, linux-3.12 will be released and aufs3.12 too.
 When aufs3.12 is released, I will stop maintaining aufs3.2, aufs3.x.2
 and aufs3.4 branches. Aufs3.[5-7] are already stopped, so the new base
 (the oldest supported version) version will be aufs3.8.
 But I am considering when I stop aufs3.8. Currently I am not sure when
 it will be. It may be same time with aufs3.2, or later much more.
 If I stop aufs3.8 when linux-3.12 is released, then the new base version
 will be aufs3.9.

linux-3.12 has come and aufs3.{2,2.x,4,8} are gone.
In next aufs release, aufs3.12 will appear and the new base version will
be aufs3.9.


J. R. Okajima

--
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk