linux-kernel - linux-next: build failure after merge of the device-mapper tree

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-next>] [day] [month] [year] [list]

Message-Id: <20100802113148.e0b70b34.sfr@canb.auug.org.au>
Date:	Mon, 2 Aug 2010 11:31:48 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Alasdair G Kergon <agk@...hat.com>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Milan Broz <mbroz@...hat.com>
Subject: linux-next: build failure after merge of the device-mapper tree

Hi Alasdair,

After merging the device-mapper tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

drivers/md/dm-crypt.c: In function 'crypt_ctr_cipher':
drivers/md/dm-crypt.c:1095: error: 'bad_mem' undeclared (first use in this function)

Caused by commit 460328b294ddd132945bdf536a9130f2d6cd6ace
("dm-crypt-simplify-crypt_ctr").

Please do test builds ... "No functional change in this patch." :-(

I will use the device-mapper tree from next-20100730 for today.

P.S. the patch summaries could be more informative ... i.e. you should
put "Subject:" lines in the patches.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped