[Unionfs] Panic in unionfs 2.2.4

[Lucas C. Villa Real]

On Sun, Mar 30, 2008 at 6:26 PM, Erez Zadok <ezk at cs.sunysb.edu> wrote:
> In message <20286507.735771206579536200.JavaMail.root at tahiti.vyatta.com>, Bob Gilligan writes:
>  [...]
>
> > And I see the panic too in unionfs-2.3.1 running on our 2.6.23 kernel.  It is the same panic signature as before:  BUG at include/linux/dcache.h:322
>  >
>  > I've filed a bug report on the problem:
>  >
>  > https://bugzilla.filesystems.org/show_bug.cgi?id=611
>  >
>  > Bob.
>
>  Bob, below is a fix to your bug #611.  Please verify it on your setup.
>  Thanks for the step-by-step tickle-the-bug script: it was very helpful.
>
>  Lucas, and others who've seen similar bugs, please let me know if the small
>  patch below fixes your oopses or not.

Hi Erez,

The patch indeed fixes the bug described by Bob. However, my setup
still triggers a kernel panic when using the chrooted
environment that we have in GoboLinux. I had to implement a temporary
backend for unionfs-fuse, but it would be really great to have that
fixed when using unionfs too.

I can provide you information on how to reproduce that, or even a
remote account if that makes things easier for you.

Kind regards,

-- 
Lucas
powered by /dev/dsp