| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20230227205542.GB4062527@hu-bjorande-lv.qualcomm.com>
Date: Mon, 27 Feb 2023 12:55:42 -0800
From: Bjorn Andersson <quic_bjorande@...cinc.com>
To: Sarannya S <quic_sarannya@...cinc.com>
CC: <arnaud.pouliquen@...s.st.com>, <swboyd@...omium.org>,
<quic_clew@...cinc.com>, <mathieu.poirier@...aro.org>,
<linux-kernel@...r.kernel.org>, <linux-arm-msm@...r.kernel.org>,
<linux-remoteproc@...r.kernel.org>,
Deepak Kumar Singh <quic_deesin@...cinc.com>,
Bjorn Andersson <andersson@...nel.org>
Subject: Re: [PATCH V5 3/3] rpmsg: char: Add TIOCMGET/TIOCMSET ioctl support
On Tue, Feb 21, 2023 at 09:26:02PM +0530, Sarannya S wrote:
> Add TICOMGET and TIOCMSET ioctl support for rpmsg char device nodes
> to get/set the low level transport signals.
Please update subjet and this commit message as well.
>
> Signed-off-by: Chris Lew <quic_clew@...cinc.com>
> Signed-off-by: Deepak Kumar Singh <quic_deesin@...cinc.com>
> Signed-off-by: Sarannya S <quic_sarannya@...cinc.com>
> ---
> drivers/rpmsg/rpmsg_char.c | 60 +++++++++++++++++++++++++++++++++++++++-------
> include/uapi/linux/rpmsg.h | 11 +++++++++
> 2 files changed, 63 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/rpmsg/rpmsg_char.c b/drivers/rpmsg/rpmsg_char.c
> index 3e0b8f3..fdcb4ff 100644
> --- a/drivers/rpmsg/rpmsg_char.c
> +++ b/drivers/rpmsg/rpmsg_char.c
> @@ -23,6 +23,7 @@
> #include <linux/rpmsg.h>
> #include <linux/skbuff.h>
> #include <linux/slab.h>
> +#include <linux/termios.h>
> #include <linux/uaccess.h>
> #include <uapi/linux/rpmsg.h>
>
> @@ -68,6 +69,8 @@ struct rpmsg_eptdev {
> struct sk_buff_head queue;
> wait_queue_head_t readq;
>
> + u32 remote_signals;
> + bool flow_control;
> };
>
> int rpmsg_chrdev_eptdev_destroy(struct device *dev, void *data)
> @@ -109,7 +112,22 @@ static int rpmsg_ept_cb(struct rpmsg_device *rpdev, void *buf, int len,
> skb_queue_tail(&eptdev->queue, skb);
> spin_unlock(&eptdev->queue_lock);
>
> - /* wake up any blocking processes, waiting for new data */
Is this comment no longer valid?
> + wake_up_interruptible(&eptdev->readq);
> +
> + return 0;
> +}
> +
> +static int rpmsg_ept_flow_cb(struct rpmsg_device *rpdev, void *priv, bool enable)
> +{
> + struct rpmsg_eptdev *eptdev = priv;
> +
> + if (enable)
> + eptdev->remote_signals = RPMSG_FLOW_CONTROL_ON;
> + else
> + eptdev->remote_signals = 0;
> +
> + eptdev->flow_control = true;
So remote_signals is the state of the remote's requested flow control
and flow_control is carrying the information that the flow control has
been requested, to interrupt poll.
I think something like remote_flow and remote_flow_updated would make
that more intuitive.
Also, remote_signals can be bool and you can just assign enable, no need
for the conditional.
> +
> wake_up_interruptible(&eptdev->readq);
>
> return 0;
> @@ -146,6 +164,7 @@ static int rpmsg_eptdev_open(struct inode *inode, struct file *filp)
> return -EINVAL;
> }
>
> + ept->flow_cb = rpmsg_ept_flow_cb;
> eptdev->ept = ept;
> filp->private_data = eptdev;
> mutex_unlock(&eptdev->ept_lock);
> @@ -166,6 +185,7 @@ static int rpmsg_eptdev_release(struct inode *inode, struct file *filp)
> eptdev->ept = NULL;
> }
> mutex_unlock(&eptdev->ept_lock);
> + eptdev->flow_control = false;
>
> /* Discard all SKBs */
> skb_queue_purge(&eptdev->queue);
> @@ -279,6 +299,9 @@ static __poll_t rpmsg_eptdev_poll(struct file *filp, poll_table *wait)
> if (!skb_queue_empty(&eptdev->queue))
> mask |= EPOLLIN | EPOLLRDNORM;
>
> + if (eptdev->flow_control)
> + mask |= EPOLLPRI;
> +
> mask |= rpmsg_poll(eptdev->ept, filp, wait);
>
> return mask;
> @@ -289,14 +312,35 @@ static long rpmsg_eptdev_ioctl(struct file *fp, unsigned int cmd,
> {
> struct rpmsg_eptdev *eptdev = fp->private_data;
>
> - if (cmd != RPMSG_DESTROY_EPT_IOCTL)
> - return -EINVAL;
> -
> - /* Don't allow to destroy a default endpoint. */
> - if (eptdev->default_ept)
> - return -EINVAL;
> + bool set;
> + u32 val;
> + int ret;
> +
> + switch (cmd) {
> + case RPMSG_GET_SIGNAL_IOCTL:
Signals is a glink name for this, how about:
RPMSG_GET_OUTGOING_FLOWCONTROL
> + eptdev->flow_control = false;
> + ret = put_user(eptdev->remote_signals, (int __user *)arg);
> + break;
> + case RPMSG_SET_SIGNAL_IOCTL:
RPMSG_SET_INCOMING_FLOWCONTROL
> + ret = get_user(val, (int __user *)arg);
> + if (ret)
> + break;
> + set = (val & RPMSG_FLOW_CONTROL_ON) ? true : false;
The reason for only considering some bit(s) in the argument is to allow
for future expansion, but unless you validate that those bits are unused
by the caller you could end up with clients passing unexpected bits in
~1, effectively preventing such future modifications.
So if we're masking out the state, then we need to also reject (arg &
~1). But I would prefer that we instead treat it as a boolean and do:
set = !!arg;
> + ret = rpmsg_set_flow_control(eptdev->ept, set);
> + break;
> + case RPMSG_DESTROY_EPT_IOCTL:
> + /* Don't allow to destroy a default endpoint. */
> + if (eptdev->default_ept) {
> + ret = -EINVAL;
> + break;
> + }
> + ret = rpmsg_chrdev_eptdev_destroy(&eptdev->dev, NULL);
> + break;
> + default:
> + ret = -EINVAL;
> + }
>
> - return rpmsg_chrdev_eptdev_destroy(&eptdev->dev, NULL);
> + return ret;
> }
>
> static const struct file_operations rpmsg_eptdev_fops = {
> diff --git a/include/uapi/linux/rpmsg.h b/include/uapi/linux/rpmsg.h
> index 1637e68..e9aa6b9 100644
> --- a/include/uapi/linux/rpmsg.h
> +++ b/include/uapi/linux/rpmsg.h
> @@ -10,6 +10,7 @@
> #include <linux/types.h>
>
> #define RPMSG_ADDR_ANY 0xFFFFFFFF
> +#define RPMSG_FLOW_CONTROL_ON 0x001
>
> /**
> * struct rpmsg_endpoint_info - endpoint info representation
> @@ -43,4 +44,14 @@ struct rpmsg_endpoint_info {
> */
> #define RPMSG_RELEASE_DEV_IOCTL _IOW(0xb5, 0x4, struct rpmsg_endpoint_info)
>
> +/**
> + * Get the remote rpmsg char device's flow control signal.
s/signal/state/
> + */
> +#define RPMSG_GET_SIGNAL_IOCTL _IOW(0xb5, 0x5, struct rpmsg_endpoint_info)
> +
> +/**
> + * Set the flow control for the local rpmsg char device.
> + */
> +#define RPMSG_SET_SIGNAL_IOCTL _IOW(0xb5, 0x6, struct rpmsg_endpoint_info)
> +
Regards,
Bjorn
> #endif
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
>
Powered by blists - more mailing lists