From: Eric Biggers <ebiggers@kernel.org>
To: keyrings@vger.kernel.org, David Howells <dhowells@redhat.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
linux-fscrypt@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KEYS: user: Align the payload buffer
Date: Tue, 19 Feb 2019 23:08:01 +0000 [thread overview]
Message-ID: <20190219230800.GD12177@gmail.com> (raw)
In-Reply-To: <20190207233509.GA125156@gmail.com>
On Thu, Feb 07, 2019 at 03:35:09PM -0800, Eric Biggers wrote:
> On Mon, Jan 14, 2019 at 07:37:16PM -0800, Eric Biggers wrote:
> > From: Eric Biggers <ebiggers@google.com>
> >
> > Align the payload of "user" and "logon" keys so that users of the
> > keyrings service can access it as a struct that requires more than
> > 2-byte alignment. fscrypt currently does this which results in the read
> > of fscrypt_key::size being misaligned as it needs 4-byte alignment.
> >
> > Align to __alignof__(u64) rather than __alignof__(long) since in the
> > future it's conceivable that people would use structs beginning with
> > u64, which on some platforms would require more than 'long' alignment.
> >
> > Reported-by: Aaro Koskinen <aaro.koskinen@iki.fi>
> > Fixes: 2aa349f6e37c ("[PATCH] Keys: Export user-defined keyring operations")
> > Fixes: 88bd6ccdcdd6 ("ext4 crypto: add encryption key management facilities")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
> > ---
> > include/keys/user-type.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/include/keys/user-type.h b/include/keys/user-type.h
> > index e098cbe27db54..12babe9915944 100644
> > --- a/include/keys/user-type.h
> > +++ b/include/keys/user-type.h
> > @@ -31,7 +31,7 @@
> > struct user_key_payload {
> > struct rcu_head rcu; /* RCU destructor */
> > unsigned short datalen; /* length of this data */
> > - char data[0]; /* actual data */
> > + char data[0] __aligned(__alignof__(u64)); /* actual data */
> > };
> >
> > extern struct key_type key_type_user;
> > --
> > 2.20.1
> >
>
> Ping. David, are you planning to apply this?
>
> - Eric
Ping.
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: keyrings@vger.kernel.org, David Howells <dhowells@redhat.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
linux-fscrypt@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KEYS: user: Align the payload buffer
Date: Tue, 19 Feb 2019 15:08:01 -0800 [thread overview]
Message-ID: <20190219230800.GD12177@gmail.com> (raw)
In-Reply-To: <20190207233509.GA125156@gmail.com>
On Thu, Feb 07, 2019 at 03:35:09PM -0800, Eric Biggers wrote:
> On Mon, Jan 14, 2019 at 07:37:16PM -0800, Eric Biggers wrote:
> > From: Eric Biggers <ebiggers@google.com>
> >
> > Align the payload of "user" and "logon" keys so that users of the
> > keyrings service can access it as a struct that requires more than
> > 2-byte alignment. fscrypt currently does this which results in the read
> > of fscrypt_key::size being misaligned as it needs 4-byte alignment.
> >
> > Align to __alignof__(u64) rather than __alignof__(long) since in the
> > future it's conceivable that people would use structs beginning with
> > u64, which on some platforms would require more than 'long' alignment.
> >
> > Reported-by: Aaro Koskinen <aaro.koskinen@iki.fi>
> > Fixes: 2aa349f6e37c ("[PATCH] Keys: Export user-defined keyring operations")
> > Fixes: 88bd6ccdcdd6 ("ext4 crypto: add encryption key management facilities")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
> > ---
> > include/keys/user-type.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/include/keys/user-type.h b/include/keys/user-type.h
> > index e098cbe27db54..12babe9915944 100644
> > --- a/include/keys/user-type.h
> > +++ b/include/keys/user-type.h
> > @@ -31,7 +31,7 @@
> > struct user_key_payload {
> > struct rcu_head rcu; /* RCU destructor */
> > unsigned short datalen; /* length of this data */
> > - char data[0]; /* actual data */
> > + char data[0] __aligned(__alignof__(u64)); /* actual data */
> > };
> >
> > extern struct key_type key_type_user;
> > --
> > 2.20.1
> >
>
> Ping. David, are you planning to apply this?
>
> - Eric
Ping.
next prev parent reply other threads:[~2019-02-19 23:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 3:37 [PATCH] KEYS: user: Align the payload buffer Eric Biggers
2019-01-15 3:37 ` Eric Biggers
2019-01-15 19:19 ` Aaro Koskinen
2019-01-15 19:19 ` Aaro Koskinen
2019-02-07 23:35 ` Eric Biggers
2019-02-07 23:35 ` Eric Biggers
2019-02-19 23:08 ` Eric Biggers [this message]
2019-02-19 23:08 ` Eric Biggers
2019-02-20 13:32 ` David Howells
2019-02-20 13:32 ` David Howells
2019-02-20 13:32 ` David Howells
2019-02-20 13:52 ` David Laight
2019-02-20 13:52 ` David Laight
2019-02-20 14:09 ` David Howells
2019-02-20 20:50 ` James Morris
2019-02-20 20:50 ` James Morris
2019-02-20 21:37 ` David Howells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190219230800.GD12177@gmail.com \
--to=ebiggers@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=dhowells@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.