From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Fuqian Huang <huangfq.daxian@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] tty: rocket: Remove the rp_ioctl
Date: Wed, 17 Apr 2019 08:46:29 +0200 [thread overview]
Message-ID: <20190417064629.GA19549@kroah.com> (raw)
In-Reply-To: <06427d24-535b-e116-51e0-d98565a8fda1@suse.cz>
On Wed, Apr 17, 2019 at 08:27:41AM +0200, Jiri Slaby wrote:
> On 16. 04. 19, 16:53, Fuqian Huang wrote:
> > --- a/drivers/tty/rocket.c
> > +++ b/drivers/tty/rocket.c
> ...
> > -/* IOCTL call handler into the driver */
> > -static int rp_ioctl(struct tty_struct *tty,
> > - unsigned int cmd, unsigned long arg)
> > -{
> > - struct r_port *info = tty->driver_data;
> > - void __user *argp = (void __user *)arg;
> > - int ret = 0;
> > -
> > - if (cmd != RCKP_GET_PORTS && rocket_paranoia_check(info, "rp_ioctl"))
> > - return -ENXIO;
> > -
> > - switch (cmd) {
> > - case RCKP_GET_STRUCT:
> > - if (copy_to_user(argp, info, sizeof (struct r_port)))
> > - ret = -EFAULT;
> > - break;
>
> I am not sure what Greg meant, but I had only this particular ioctl on
> mind when I was writing about removal. The other ones might be used _in
> theory_. Even though they are not exposed to userspace either. So if
> they are not source of potential issues, I would keep them:
I was just meaning that one specific ioctl, not the whole thing.
Although dropping all of these custom ioctls is probably the right thing
to do in the long-run, for now, let's just get rid of the problem one.
thanks,
greg k-h
next prev parent reply other threads:[~2019-04-17 6:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 14:53 [PATCH v4] tty: rocket: Remove the rp_ioctl Fuqian Huang
2019-04-17 6:27 ` Jiri Slaby
2019-04-17 6:46 ` Greg Kroah-Hartman [this message]
2019-04-17 6:52 ` Jiri Slaby
2019-04-17 6:56 ` Jiri Slaby
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=20190417064629.GA19549@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=huangfq.daxian@gmail.com \
--cc=jslaby@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox