Junjiro, > > Ok thanks, that's what I did in the previous step (not applying > > aufs3-loopback.patch), but it still BUGs. > > Your (previous) problem came from the conflicted loop.h, right? > If you still have the same BUG msg, then it means you didn't solve the > conflict. Don't you agree?
Ok, I'm pretty sure the issue has to do with loop.h as you say. I compile aufs against standard kernel loop.h, and later compile loop-aes, that CHANGES that loop.h file (but too late, aufs already compiled against wrong header). Looking in detail, the loop_device struct in loop.h from kernel and from loop-aes are very similar, but stuff are inserted right before "lo_backing_file" (which was were we saw the BUG). I'll then try patching kernel with loop-aes BEFORE compiling aufs... Hopefully it will work, I'll report as soon as I confirm that. Thanks again, François. ------------------------------------------------------------------------------ WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
