linux-kernel - Re: ext4-stable build failure (Re: Ext4 tree backports for 2.6.27.10 and 2.6.28)

lists.openwall.net		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 linux-hardening linux-cve-announce 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]

Message-ID: <20090117230322.GA25943@mit.edu>
Date:	Sat, 17 Jan 2009 18:03:22 -0500
From:	Theodore Tso <tytso@....edu>
To:	Malte Schröder <maltesch@....de>
Cc:	linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
	stable@...nel.org
Subject: Re: ext4-stable build failure (Re: Ext4 tree backports for
	2.6.27.10 and 2.6.28)

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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/