From: Ted Ts'o <tytso@mit.edu>
To: sedat.dilek@gmail.com
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org, sfr@canb.auug.org.au,
Arnd Bergmann <arnd@arndb.de>,
Avinash Kurup <kurup.avinash@gmail.com>
Subject: Re: [next-20101038] Call trace in ext4
Date: Thu, 28 Oct 2010 16:37:06 -0400 [thread overview]
Message-ID: <20101028203706.GD28126@thunk.org> (raw)
In-Reply-To: <AANLkTimw9Vwzy4MXO1t7TnJfwTwYtWcfj0D=Zx8O72cY@mail.gmail.com>
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
next prev parent reply other threads:[~2010-10-28 20:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 10:05 [next-20101038] Call trace in ext4 Sedat Dilek
2010-10-28 10:34 ` [next-20101028] " Sedat Dilek
2010-10-28 15:08 ` Sedat Dilek
2010-10-28 15:27 ` Ted Ts'o
2010-10-28 17:52 ` [next-20101038] " Markus Trippelsdorf
2010-10-28 18:01 ` Ted Ts'o
2010-10-28 18:16 ` Eric Sandeen
2010-10-28 19:32 ` Ted Ts'o
2010-10-28 19:36 ` Eric Sandeen
2010-10-28 19:54 ` Ted Ts'o
2010-10-28 19:54 ` Sedat Dilek
2010-10-28 20:05 ` Ted Ts'o
2010-10-28 20:15 ` Sedat Dilek
2010-10-28 20:37 ` Ted Ts'o [this message]
2010-10-28 21:02 ` Sedat Dilek
2010-10-28 21:06 ` Ted Ts'o
2010-10-28 21:17 ` Sedat Dilek
2010-10-28 18:20 ` Sedat Dilek
2010-10-28 18:34 ` Sedat Dilek
2010-10-28 18:55 ` Ted Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101028203706.GD28126@thunk.org \
--to=tytso@mit.edu \
--cc=arnd@arndb.de \
--cc=kurup.avinash@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).