From: Kent Gibson <warthog618@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
linux-gpio@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2] gpiolib: Fix line event handling in syscall compatible mode
Date: Tue, 15 Sep 2020 07:05:26 +0800 [thread overview]
Message-ID: <20200914230526.GA4138@sol> (raw)
In-Reply-To: <20200914143743.39871-1-andriy.shevchenko@linux.intel.com>
On Mon, Sep 14, 2020 at 05:37:43PM +0300, Andy Shevchenko wrote:
> The introduced line even handling ABI in the commit
>
s/even/event/
> 61f922db7221 ("gpio: userspace ABI for reading GPIO line events")
>
> missed the fact that 64-bit kernel may serve for 32-bit applications.
> In such case the very first check in the lineevent_read() will fail
> due to alignment differences.
>
> To workaround this introduce lineeven_to_user() helper which returns actual
> size of the structure and copies its content to user if asked.
>
s/lineeven_to_user/lineevent_get_size/
and
s/structure and copies its content to user if asked/structure in userspace/
> Fixes: 61f922db7221 ("gpio: userspace ABI for reading GPIO line events")
> Suggested-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> v2: moved to just calculate size (Arnd, Kent), added good comment (Arnd)
> drivers/gpio/gpiolib-cdev.c | 34 ++++++++++++++++++++++++++++++----
> 1 file changed, 30 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpio/gpiolib-cdev.c b/drivers/gpio/gpiolib-cdev.c
> index e6c9b78adfc2..95af4a470f1e 100644
> --- a/drivers/gpio/gpiolib-cdev.c
> +++ b/drivers/gpio/gpiolib-cdev.c
> @@ -423,6 +423,21 @@ static __poll_t lineevent_poll(struct file *file,
> return events;
> }
>
> +static ssize_t lineevent_get_size(void)
> +{
> +#ifdef __x86_64__
> + /* i386 has no padding after 'id' */
> + if (in_ia32_syscall()) {
> + struct compat_gpioeevent_data {
> + compat_u64 timestamp;
> + u32 id;
> + };
> +
> + return sizeof(struct compat_gpioeevent_data);
> + }
> +#endif
> + return sizeof(struct gpioevent_data);
> +}
>
It can return size_t now.
> static ssize_t lineevent_read(struct file *file,
> char __user *buf,
> @@ -432,9 +447,20 @@ static ssize_t lineevent_read(struct file *file,
> struct lineevent_state *le = file->private_data;
> struct gpioevent_data ge;
> ssize_t bytes_read = 0;
> + ssize_t ge_size;
Similarly here.
> int ret;
>
> - if (count < sizeof(ge))
> + /*
> + * When compatible system call is being used the struct gpioevent_data,
> + * in case of at least ia32, has different size due to the alignment
> + * differences. Because we have first member 64 bits followed by one of
> + * 32 bits there is no gap between them. The only problematic is the
> + * padding at the end of the data structure. Hence, we calculate the
> + * actual sizeof() and pass this as an argument to copy_to_user() to
> + * drop unneeded bytes from the output.
> + */
s/problematic/difference/
> + ge_size = lineevent_get_size();
> + if (count < ge_size)
> return -EINVAL;
>
> do {
> @@ -470,10 +496,10 @@ static ssize_t lineevent_read(struct file *file,
> break;
> }
>
> - if (copy_to_user(buf + bytes_read, &ge, sizeof(ge)))
> + if (copy_to_user(buf + bytes_read, &ge, ge_size))
> return -EFAULT;
> - bytes_read += sizeof(ge);
> - } while (count >= bytes_read + sizeof(ge));
> + bytes_read += ge_size;
> + } while (count >= bytes_read + ge_size);
>
> return bytes_read;
> }
> --
> 2.28.0
>
Cheers,
Kent.
next prev parent reply other threads:[~2020-09-14 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 14:37 [PATCH v2] gpiolib: Fix line event handling in syscall compatible mode Andy Shevchenko
2020-09-14 14:55 ` Arnd Bergmann
2020-09-14 15:01 ` Andy Shevchenko
2020-09-14 23:05 ` Kent Gibson [this message]
2020-09-15 9:11 ` Andy Shevchenko
2020-09-15 9:20 ` Andy Shevchenko
2020-09-15 12:18 ` Kent Gibson
2020-09-15 12:56 ` Andy Shevchenko
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=20200914230526.GA4138@sol \
--to=warthog618@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox