From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org,
Alexandre Courbot <acourbot@nvidia.com>,
Michael Welling <mwelling@ieee.org>,
Markus Pargmann <mpa@pengutronix.de>,
Lee Campbell <leecam@google.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Bamvor Jian Zhang <bamvor.zhangjian@linaro.org>,
Grant Likely <grant.likely@linaro.org>,
Arnd Bergmann <arnd@arndb.de>, Mark Brown <broonie@kernel.org>,
Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH 1/4] gpio: userspace ABI for reading/writing GPIO lines
Date: Wed, 29 Jun 2016 10:53:13 +0200 [thread overview]
Message-ID: <2026706.RhdqQzbNxG@ws-stein> (raw)
In-Reply-To: <1464868289-1766-1-git-send-email-linus.walleij@linaro.org>
On Thursday 02 June 2016 13:51:26, Linus Walleij wrote:
> This adds a userspace ABI for reading and writing GPIO lines.
> The mechanism returns an anonymous file handle to a request
> to read/write n offsets from a gpiochip. This file handle
> in turn accepts two ioctl()s: one that reads and one that
> writes values to the selected lines.
> [...]
> +static int linehandle_create(struct gpio_device *gdev, void __user *ip)
> +{
> + struct gpiohandle_request handlereq;
> + struct linehandle_state *lh;
> + int fd, i, ret;
> +
> + if (copy_from_user(&handlereq, ip, sizeof(handlereq)))
> + return -EFAULT;
> + if ((handlereq.lines == 0) || (handlereq.lines > GPIOHANDLES_MAX))
> + return -EINVAL;
> +
> + lh = kzalloc(sizeof(*lh), GFP_KERNEL);
> + if (!lh)
> + return -ENOMEM;
> + lh->gdev = gdev;
> + get_device(&gdev->dev);
> +
> + /* Make sure this is terminated */
> + handlereq.consumer_label[sizeof(handlereq.consumer_label)-1] = '\0';
> + if (strlen(handlereq.consumer_label)) {
> + lh->label = kstrdup(handlereq.consumer_label,
> + GFP_KERNEL);
> + if (!lh->label) {
> + ret = -ENOMEM;
> + goto out_free_lh;
> + }
> + }
> +
> + /* Request each GPIO */
> + for (i = 0; i < handlereq.lines; i++) {
> + u32 offset = handlereq.lineoffsets[i];
> + u32 lflags = handlereq.flags;
> + struct gpio_desc *desc;
> +
> + desc = &gdev->descs[offset];
> + ret = gpiod_request(desc, lh->label);
> + if (ret)
> + goto out_free_descs;
> + lh->descs[i] = desc;
> +
> + if (lflags & GPIOHANDLE_REQUEST_ACTIVE_LOW)
> + set_bit(FLAG_ACTIVE_LOW, &desc->flags);
> + if (lflags & GPIOHANDLE_REQUEST_OPEN_DRAIN)
> + set_bit(FLAG_OPEN_DRAIN, &desc->flags);
> + if (lflags & GPIOHANDLE_REQUEST_OPEN_SOURCE)
> + set_bit(FLAG_OPEN_SOURCE, &desc->flags);
> +
> + /*
> + * Lines have to be requested explicitly for input
> + * or output, else the line will be treated "as is".
> + */
> + if (lflags & GPIOHANDLE_REQUEST_OUTPUT) {
> + int val = !!handlereq.default_values[i];
> +
> + ret = gpiod_direction_output(desc, val);
> + if (ret)
> + goto out_free_descs;
> + } else if (lflags & GPIOHANDLE_REQUEST_INPUT) {
> + ret = gpiod_direction_input(desc);
> + if (ret)
> + goto out_free_descs;
> + }
> + dev_dbg(&gdev->dev, "registered chardev handle for line %d\n",
> + offset);
> + }
> + lh->numdescs = handlereq.lines;
> +
> + fd = anon_inode_getfd("gpio-linehandle",
> + &linehandle_fileops,
> + lh,
> + O_RDONLY | O_CLOEXEC);
When will linehandle_release actually be called? When we explicitely call
close(req.fd) or when application exits and all FDs will be closed anyway?
> + if (fd < 0) {
> + ret = fd;
> + goto out_free_descs;
> + }
> +
> + handlereq.fd = fd;
> + if (copy_to_user(ip, &handlereq, sizeof(handlereq)))
> + return -EFAULT;
If I'm right above doesn't that then leak lh until application eventually
exits? Userspace won't receive the newly created fd. The same would apply to
patch 3/4.
Best regards,
Alexander
next prev parent reply other threads:[~2016-06-29 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 11:51 [PATCH 1/4] gpio: userspace ABI for reading/writing GPIO lines Linus Walleij
2016-06-02 11:51 ` [PATCH 2/4] tools/gpio: add the gpio-hammer tool Linus Walleij
2016-06-02 11:51 ` [PATCH 3/4] gpio: userspace ABI for reading GPIO line events Linus Walleij
2016-06-02 11:51 ` [PATCH 4/4] tools/gpio: add the gpio-event-mon tool Linus Walleij
2016-06-02 18:12 ` [PATCH 1/4] gpio: userspace ABI for reading/writing GPIO lines Michael Welling
2016-06-29 8:53 ` Alexander Stein [this message]
2016-06-29 9:05 ` Linus Walleij
2016-06-29 9:43 ` Alexander Stein
2016-07-04 9:55 ` Linus Walleij
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=2026706.RhdqQzbNxG@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=acourbot@nvidia.com \
--cc=arnd@arndb.de \
--cc=bamvor.zhangjian@linaro.org \
--cc=broonie@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=grant.likely@linaro.org \
--cc=johan@kernel.org \
--cc=leecam@google.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mpa@pengutronix.de \
--cc=mwelling@ieee.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