On Fri, Feb 22, 2008 at 08:34:23PM +0800, Herbert Xu wrote:
> Does this patch fix the problem?
It does fix the problem on my system.
Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Fri, Feb 22, 2008 at 08:34:23PM +0800, Herbert Xu wrote:
Does this patch fix the problem?
It does fix the problem on my system.
Jan
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Thu, Feb 21, 2008 at 01:58:19AM +0800, Herbert Xu wrote:
> On Wed, Feb 20, 2008 at 06:47:58PM +0100, Milan Broz wrote:
> >
> > I just tested one affected configuration and problem was in missing
> > "chainiv.ko" module on ramdisk.
>
> Ah OK. We probably should merge chainiv into the blkcipher
On Thu, Feb 21, 2008 at 01:58:19AM +0800, Herbert Xu wrote:
On Wed, Feb 20, 2008 at 06:47:58PM +0100, Milan Broz wrote:
I just tested one affected configuration and problem was in missing
chainiv.ko module on ramdisk.
Ah OK. We probably should merge chainiv into the blkcipher
module
On Feb 20, 2008 7:58 PM, Herbert Xu <[EMAIL PROTECTED]> wrote:
> On Wed, Feb 20, 2008 at 06:47:58PM +0100, Milan Broz wrote:
> >
> > I just tested one affected configuration and problem was in missing
> > "chainiv.ko" module on ramdisk.
>
> Ah OK. We probably should merge chainiv into the
On Wed, Feb 20, 2008 at 06:47:58PM +0100, Milan Broz wrote:
>
> I just tested one affected configuration and problem was in missing
> "chainiv.ko" module on ramdisk.
Ah OK. We probably should merge chainiv into the blkcipher
module too since it's the default IV generator. I'll take
care of it.
Herbert Xu wrote:
> On Wed, Feb 20, 2008 at 12:23:21PM +0100, Milan Broz wrote:
>> It seems that some module dependency was lost,
>> dm-crypt with async crypto depends now on crypto_blkcipher module
>> for this configuration.
>>
>> Herbert, any following change required for dm-crypt or it is only
On Wed, Feb 20, 2008 at 12:23:21PM +0100, Milan Broz wrote:
>
> It seems that some module dependency was lost,
> dm-crypt with async crypto depends now on crypto_blkcipher module
> for this configuration.
>
> Herbert, any following change required for dm-crypt or it is only
> crypto subsystem
Michael S. Tsirkin wrote:
> I am booting a thinkpad T60p off of an encrypted disk (with crypto
> modules in initramfs).
> This works fine in 2.6.24, but in both 2.6.25-rc1 and 2.6.25-rc2
> won't boot with the following messages on the console
> (copied by hand, sorry about typos):
>
Michael S. Tsirkin wrote:
I am booting a thinkpad T60p off of an encrypted disk (with crypto
modules in initramfs).
This works fine in 2.6.24, but in both 2.6.25-rc1 and 2.6.25-rc2
won't boot with the following messages on the console
(copied by hand, sorry about typos):
On Wed, Feb 20, 2008 at 12:23:21PM +0100, Milan Broz wrote:
It seems that some module dependency was lost,
dm-crypt with async crypto depends now on crypto_blkcipher module
for this configuration.
Herbert, any following change required for dm-crypt or it is only
crypto subsystem issue?
Herbert Xu wrote:
On Wed, Feb 20, 2008 at 12:23:21PM +0100, Milan Broz wrote:
It seems that some module dependency was lost,
dm-crypt with async crypto depends now on crypto_blkcipher module
for this configuration.
Herbert, any following change required for dm-crypt or it is only
crypto
On Wed, Feb 20, 2008 at 06:47:58PM +0100, Milan Broz wrote:
I just tested one affected configuration and problem was in missing
chainiv.ko module on ramdisk.
Ah OK. We probably should merge chainiv into the blkcipher
module too since it's the default IV generator. I'll take
care of it.
On Feb 20, 2008 7:58 PM, Herbert Xu [EMAIL PROTECTED] wrote:
On Wed, Feb 20, 2008 at 06:47:58PM +0100, Milan Broz wrote:
I just tested one affected configuration and problem was in missing
chainiv.ko module on ramdisk.
Ah OK. We probably should merge chainiv into the blkcipher
module
14 matches
Mail list logo