Fran ois:
> Here is the output. There are some non-printable "filled-squarish"
> characters after "fname" that I replace by "#":
:::
> aufs au_test_loopback_overlap:48:exe[289]: lo {num 0, f 0x200003, fname
> ######/live/image/live/filesystem.squashfs, file (null), vfile
> ffff88000340c000, state -30720}
Thanks for testing.
Now it becomes clear that the "struct loop_device" object is totaly
broken, and aufs cannot retrieve the necessary info from it.
The most possible cause is mixing these.
- aufs module is built from the patched kernel files
- but the running kernel is built from the unpatched files
But you have carefully confirmed that this is not your case, I know.
Another possible cause will be... An optimizer?
How did you compile aufs module? Did you use excatly same compiler
options to building kernel?
Where is your image file "filesystem.squashfs"? Is it inside of another
loopback-mounted filesystem, or another fs on a block device such as
/dev/sda1?
And may I ask you trying one more debug print patch?
J. R. Okajima
------------------------------------------------------------------------------
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
