[dm-devel] Re: [BUG] dmsetup table output changed from 2.6.18 to 2.6.19-rc3 and breaks yaird.
Alasdair G Kergon
agk at redhat.com
Mon Oct 30 19:15:54 UTC 2006
On Mon, Oct 30, 2006 at 11:00:29AM -0800, Linus Torvalds wrote:
> (maybe something like this trivial one? Totally untested, but it would
> seem to be the sane approach)
> diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c
> index a625576..645e3ce 100644
> --- a/drivers/md/dm-crypt.c
> +++ b/drivers/md/dm-crypt.c
> @@ -925,8 +925,7 @@ static int crypt_status(struct dm_target
> break;
>
> case STATUSTYPE_TABLE:
> - cipher = crypto_blkcipher_name(cc->tfm);
> -
> + cipher = cc->cipher;
> chainmode = cc->chainmode;
>
> if (cc->iv_mode)
>
>
Looks correct.
The point of STATUSTYPE_TABLE is to return (readable) output to userspace in
a format that the crypt_ctr() function would accept back in.
So crypt_ctr() now stores a private copy of cipher and chainmode for
crypt_status() to regurgitate when requested.
Alasdair
--
agk at redhat.com
More information about the dm-devel
mailing list