lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 28 Oct 2010 23:02:14 +0200
From:	Sedat Dilek <>
To:	"Ted Ts'o" <>,,
	Markus Trippelsdorf <>,
	LKML <>,,, Arnd Bergmann <>,
	Avinash Kurup <>
Subject: Re: [next-20101038] Call trace in ext4

On Thu, Oct 28, 2010 at 10:37 PM, Ted Ts'o <> 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 -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 -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists