linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Malte Schröder" <maltesch@gmx.de>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@kernel.org
Subject: ext4-stable build failure (Re: Ext4 tree backports for 2.6.27.10 and 2.6.28)
Date: Sat, 17 Jan 2009 23:16:51 +0100	[thread overview]
Message-ID: <20090117231651.78b2cce5@highlander.home.lan> (raw)
In-Reply-To: <E1LOG9D-0006h4-7R@closure.thunk.org>

[-- Attachment #1: Type: text/plain, Size: 660 bytes --]

Hello,

On Sat, 17 Jan 2009 13:43:55 -0500
"Theodore Ts'o" <tytso@mit.edu> wrote:

> 
> I've created a couple of ext4 backport branches which have been uploaded
> to the ext4 git tree:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git 
>    http://git.kernel.org/?p=linux/kernel/git/tytso/ext4.git
> 

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.

Regards
Malte Schröder

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-01-17 22:16 UTC|newest]

Thread overview: 18+ 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 ` Malte Schröder [this message]
2009-01-17 23:03   ` ext4-stable build failure (Re: Ext4 tree backports for 2.6.27.10 and 2.6.28) 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=20090117231651.78b2cce5@highlander.home.lan \
    --to=maltesch@gmx.de \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=tytso@mit.edu \
    /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).