Hello Preeti If you do the same by using Fanotify, you don't even have to touch the kernel and your program can run completely in user space.
Daniel Alder On 21.04.2012 09:06, sf...@users.sourceforge.net wrote: > > Hello Preeti, > > Preeti Sharma: >> I am new to aufs and this list. I just began looking at the aufs3.0 code >> and noticed coo= is ignored . >> Is there a patch for this ? > > The copyup-on-open feature was dropped when aufs grew up to aufs2. > http://sourceforge.net/mailarchive/message.php?msg_id=21374168 > > In other words, it is the feature which existed in aufs1 only. > And there is no patch for it. > > If you really want the coo feature in aufs3, then I'd suggest you try > the simplest way, which is, > - enable CONFIG_KPROBES. > - write another module which is based upon kprobes. > + read linux/Documentation/kprobes.txt > + write a jprobe function for au_do_open() which is an aufs internal > function. > + in the jprobe function, execute a harmless but forcing aufs to > copyup operation such like chmod/chown() to the current > mode/owner/group, or utime() for atime. > > In this approach, you don't have to modify the aufs source files, just > create a small module which sets a hook to the aufs internal function. > > > J. R. Okajima > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2
