Messages in this thread | | | Date | Thu, 28 Oct 2010 23:02:14 +0200 | Subject | Re: [next-20101038] Call trace in ext4 | From | Sedat Dilek <> |
| |
On Thu, Oct 28, 2010 at 10:37 PM, Ted Ts'o <tytso@mit.edu> wrote: > On Thu, Oct 28, 2010 at 10:15:00PM +0200, Sedat Dilek wrote: >> >> I created a new ext4.ko via "make M=fs/ext4" in the build-dir and >> copied the the kernel-module to /lib/modules/$(uname >> -r)/kernel/fs/ext4/, is that not enough? > > It might not be. Some distributions include modules in the initial > ramdisk, and load the module from the initrd, simply dropping the > module in /lib/modules/<kver>/... might not be enough. So recreating > the initrd and then rebooting might be enough. > > Certainly if you drop it there on a running kernel, if you don't > unload the module (before unmounting all of your ext4 file systems), > and then reload the module, *definitely* just copying a module into > /lib/modules.... without making sure the module is reloaded, you'll > still have the old module. > > - Ted >
Grrr, did not think of ext4 kernel-module be in initrd.img.
OK, I have recreated a new one:
$ update-initramfs -k 2.6.36-git11.sd.1-686 -c
I could copy a complete linux-2.6 GIT tree within my $HOME/src, looks good.
Any other test-case you can suggest to be sure things work as expected, now?
BTW, feel free to add:
Reported-andtested-by: Sedat Dilek <sedat.dilek@gmail.com>
- Sedat - -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |