From: Theodore Tso <tytso@mit.edu>
To: "Malte Schröder" <maltesch@gmx.de>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: ext4-stable build failure (Re: Ext4 tree backports for 2.6.27.10 and 2.6.28)
Date: Sat, 17 Jan 2009 18:03:22 -0500 [thread overview]
Message-ID: <20090117230322.GA25943@mit.edu> (raw)
In-Reply-To: <20090117231651.78b2cce5@highlander.home.lan>
On Sat, Jan 17, 2009 at 11:16:51PM +0100, Malte Schröder wrote:
>
> kernel 2.6.28 with ext4-stable fails to build for SMP on AMD64.
>
> Building modules, stage 2.
> MODPOST 905 modules
> ERROR: "inode_lock" [fs/ext4/ext4.ko] undefined!
>
> I had to revert 5cb8613e44b6e6c77dcf231d691b96c91a5adeab (ext4: Add a
> delayed allocation debugging ioctl), after that it works.
I see the problem; inode_lock isn't currently an exported symbol, and
I generally don't compile ext4 as a module, so I didn't notice the
problem. The patch in question is a debugging patch that is never
meant for mainline or a for-stable series, so the simplest thing to do
for now is just to revert the patch. I'll look into a module-friendly
way of accomplishing the same goal.
Regards,
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Theodore Tso <tytso@mit.edu>
To: "Malte Schröder" <maltesch@gmx.de>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: ext4-stable build failure (Re: Ext4 tree backports for 2.6.27.10 and 2.6.28)
Date: Sat, 17 Jan 2009 18:03:22 -0500 [thread overview]
Message-ID: <20090117230322.GA25943@mit.edu> (raw)
In-Reply-To: <20090117231651.78b2cce5@highlander.home.lan>
On Sat, Jan 17, 2009 at 11:16:51PM +0100, Malte Schröder wrote:
>
> kernel 2.6.28 with ext4-stable fails to build for SMP on AMD64.
>
> Building modules, stage 2.
> MODPOST 905 modules
> ERROR: "inode_lock" [fs/ext4/ext4.ko] undefined!
>
> I had to revert 5cb8613e44b6e6c77dcf231d691b96c91a5adeab (ext4: Add a
> delayed allocation debugging ioctl), after that it works.
I see the problem; inode_lock isn't currently an exported symbol, and
I generally don't compile ext4 as a module, so I didn't notice the
problem. The patch in question is a debugging patch that is never
meant for mainline or a for-stable series, so the simplest thing to do
for now is just to revert the patch. I'll look into a module-friendly
way of accomplishing the same goal.
Regards,
- Ted
next prev parent reply other threads:[~2009-01-17 23:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 18:43 Ext4 tree backports for 2.6.27.10 and 2.6.28 Theodore Ts'o
2009-01-17 22:16 ` ext4-stable build failure (Re: Ext4 tree backports for 2.6.27.10 and 2.6.28) Malte Schröder
2009-01-17 23:03 ` Theodore Tso [this message]
2009-01-17 23:03 ` Theodore Tso
2009-01-19 11:33 ` Ext4 tree backports for 2.6.27.10 and 2.6.28 Aneesh Kumar K.V
2009-08-30 4:25 ` Ext4 corruption that will not go away Ed Tomlinson
2009-08-30 13:15 ` LDB
2009-08-30 14:24 ` Nick Dokos
2009-08-30 23:19 ` Ed Tomlinson
2009-08-30 15:41 ` Theodore Tso
2009-01-19 11:33 ` Ext4 tree backports for 2.6.27.10 and 2.6.28 Aneesh Kumar K.V
2009-01-19 11:34 ` [PATCH] ext4: Use EXT4_GROUP_INFO_NEED_INIT_BIT during resize Aneesh Kumar K.V
2009-01-19 11:35 ` [PATCH] ext4: Use an rbtree for tracking blocks freed during transaction Aneesh Kumar K.V
2009-01-19 17:14 ` Mike Snitzer
2009-01-19 17:16 ` Mike Snitzer
2009-01-19 11:36 ` [PATCH] ext4: don't use blocks freed but not yet committed in buddy cache init Aneesh Kumar K.V
2009-01-19 11:38 ` [PATCH]ext4: Use new buffer_head flag to check uninit group bitmaps initialization Aneesh Kumar K.V
2009-01-19 11:39 ` [PATCH] ext4: Add blocks added during resize to bitmap Aneesh Kumar K.V
2009-01-22 19:50 ` [stable] Ext4 tree backports for 2.6.27.10 and 2.6.28 Greg KH
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=20090117230322.GA25943@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maltesch@gmx.de \
--cc=stable@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.