When I compile dm-io.c in /usr/src/linux-2.4.25_pre7-gss-r2/drivers/md I get the following error: gcc -D__KERNEL__ -I/usr/src/linux-2.4.25_pre7-gss-r2/include -Wall -Wstrict-prot otypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-sta ck-boundary=2 -march=athlon -nostdinc -iwithprefix include -DKBUILD_BASENAME=d m_io -DEXPORT_SYMTAB -c dm-io.c dm-io.c: In function `resize_pool': dm-io.c:88: error: `mempool_free_slab' undeclared (first use in this function) dm-io.c:88: error: (Each undeclared identifier is reported only once dm-io.c:88: error: for each function it appears in.) Reproducible: Always Steps to Reproduce: 1. Installed gs-sources-2.4.25_pre7-r2 2. make mrproper depend bzImage 3. Actual Results: I get the above compilation error Expected Results: compile without error I am attaching my config file.
Created attachment 26033 [details] My kernel configuration file
FYI: I have the crypt use flag enabled
Hi, I have done some looking around and for what I gather, it seems that the mempool_free_slab interface defintion is missing from <linux/mempool.h> Please see link at http://people.sistina.com/~thornber/patches/2.4-stable/2.4.23/2.4.23-dm1/00002.patch
I have the same problem !!!
Same problem here :( Combine that with the fact vmware isn't running properly on 2.4.22-gentoo-r7 and I'm starting to run out of kernels I can use to keep my system running safely with the features I need. Considering that 2.4.25_pre7-gss-r1 specifically added device mapper support, how could it have been released as stable when it won't even compile out of the box when that support is enabled?
Replacing the include/linux/mempool.h and mm/mempool.c files from linux-2.4.25_pre7-r2, with those in the above patch from Sistina, allowed my kernel to compile ok. We'll see how stable/functional it is :)
Been up and running since my last post with no apparent problems from the code replacement mentioned above. LVM2 has been working and stable and I haven't run into any other problems on any portion of my system since. I hope we can get the proper patches to gs-sources soon, but in the meantime following the above proceedure seems to work fine. --joe
old bug, reopen if necessary
The problem is still there and unfortunatelly it has not faded away with age
gs-sources is no longer in portage as its outdated and unmaintained. Please use gentoo-sources for 2.4 or gentoo-dev-sources for 2.6.