[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFLxGvy7WsV7Qo42yTbsZf9YnW563a0k6Yx2-NmASNtoektu_Q@mail.gmail.com>
Date: Thu, 21 Feb 2019 00:52:38 +0100
From: Richard Weinberger <richard.weinberger@...il.com>
To: Eric Biggers <ebiggers@...nel.org>
Cc: linux-fscrypt@...r.kernel.org, Satya Tangirala <satyat@...gle.com>,
"open list:ABI/API" <linux-api@...r.kernel.org>,
linux-f2fs-devel@...ts.sourceforge.net, keyrings@...r.kernel.org,
linux-mtd@...ts.infradead.org, linux-crypto@...r.kernel.org,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-ext4@...r.kernel.org, Paul Crowley <paulcrowley@...gle.com>
Subject: Re: [RFC PATCH v3 07/18] fscrypt: add FS_IOC_ADD_ENCRYPTION_KEY ioctl
On Wed, Feb 20, 2019 at 7:55 AM Eric Biggers <ebiggers@...nel.org> wrote:
> +#define FSCRYPT_FS_KEYRING_DESCRIPTION_SIZE \
> + (CONST_STRLEN("fscrypt-") + FIELD_SIZEOF(struct super_block, s_id))
> +
> +#define FSCRYPT_MK_DESCRIPTION_SIZE (2 * FSCRYPT_KEY_DESCRIPTOR_SIZE + 1)
> +
> +static void format_fs_keyring_description(
> + char description[FSCRYPT_FS_KEYRING_DESCRIPTION_SIZE],
> + const struct super_block *sb)
> +{
> + sprintf(description, "fscrypt-%s", sb->s_id);
> +}
I fear ->s_id is not the right thing.
For filesystems such as ext4 ->s_id is the name of the backing block device,
so it is per filesysem instance unique.
But this is not guaranteed. For UBIFS ->s_id is just "ubifs", always.
So the names will clash.
--
Thanks,
//richard
Powered by blists - more mailing lists