Florian Klink: > When compiling a kernel with BLK_DEV_LOOP=m and AUFS_FS=y, I see at bootup: > > aufs au_loopback_init:136:swapper/0[1]: loop_backing_file() is not defined
Ok, I see your point. Aufs will be unusable on such system. How do you think about moving "symbol_request(loop_backing_file)" from au_loopback_init() to au_test_loopback_overlap(), and no changes about Kconfig? It will postpone the symbol resolution and loading loop module until a user adds a loopback-mounted branch to aufs. Since I am afraid that disabling AUFS_BDEV_LOOP while BLK_DEV_LOOP=m will make users confused very much, I don't think it a good idea to change Kconfig as your patch. Thanx J. R. Okajima
a.patch.bz2
Description: BZip2 compressed data
------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
