linux-kernel - Re: 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4C566942.9020608@redhat.com>
Date:	Mon, 02 Aug 2010 08:44:18 +0200
From:	Milan Broz <mbroz@...hat.com>
To:	Alasdair G Kergon <agk@...hat.com>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the device-mapper tree

On 08/02/2010 03:31 AM, Stephen Rothwell wrote:
> 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)

hmmmm, Alasdair you edited that patch?
The version I sent compiled cleanly.
(moreover it is just part of patchset which is not yet fully there, seems)

Milan
--
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/