[Unionfs] unionfs-2.5_for_2.6.27-rc6 and Kernels 2.6.27 to 2.6.27.4

[Erez Zadok]

In message <4914632A.10101 at itamservices.de>, Daniel Reichelt writes:
> > Unionfs: handle partial copyup errors gracefully
> > 
> > Don't leave any dentries behind if copying up the inode (or setting its
> > permission, i.e., using TOMOYO) failed.
> > 
> > CC: Tetsuo Handa <penguin-kernel at i-love.sakura.ne.jp>
> > Signed-off-by: Erez Zadok <ezk at cs.sunysb.edu>
> > diff --git a/fs/unionfs/copyup.c b/fs/unionfs/copyup.c
> > index bbd49c8..5b6ff23 100644
> > --- a/fs/unionfs/copyup.c
> > +++ b/fs/unionfs/copyup.c
> > @@ -519,8 +519,17 @@ out_free:
> >  		dput(old_lower_dentry);
> >  	kfree(symbuf);
> 
> Sry, no improvement. Anything in particular we can do to help track down
> the issue?

OK, I'll debug it and see what's going on.  Some useful info I could use:

- what mounts do you have prior to using unionfs (cat /proc/mounts?)

- when did this problem start, at any paritcular 2.6.27-XXX release?

> Erez, what changes did you make between the unionfs releases for lx 2.6.26
> and 2.6.27? Just adjustments to changes of the kernel API or functional
> changes as well?

Only API changes, not functional ones.   I try to keep all the same version
of unionfs for all kernels functionally the same.  So basically, all unionfs
releases named, say, unionfs-2.5_for_2.6.*, should be functionally
identical.

> Cheers,
> Daniel

Erez.