From: Keith Packard <keithp@keithp.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: keithp@keithp.com, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [PATCH] usb/serial: Add compat_ioctl pass-through
Date: Thu, 27 Nov 2008 10:27:04 -0800 [thread overview]
Message-ID: <1227810424.4277.55.camel@aiko.keithp.com> (raw)
In-Reply-To: <200811271531.18498.arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 2055 bytes --]
On Thu, 2008-11-27 at 15:31 +0100, Arnd Bergmann wrote:
> On Thursday 27 November 2008, Keith Packard wrote:
> > +static long serial_compat_ioctl(struct tty_struct *tty, struct file *file,
> > + unsigned int cmd, unsigned long arg)
> > +{
> > + struct usb_serial_port *port = tty->driver_data;
> > + long retval = -ENODEV;
> > +
> > + dbg("%s - port %d, cmd 0x%.4x", __func__, port->number, cmd);
> > +
> > + WARN_ON(!port->port.count);
> > +
> > + /* pass on to the driver specific version of this function
> > + if it is available */
> > + if (port->serial->type->compat_ioctl) {
> > + lock_kernel();
> > + retval = port->serial->type->compat_ioctl(tty, file, cmd, arg);
> > + unlock_kernel();
>
> By convention, compat_ioctl functions should be called without the big kernel
> lock held.
Thanks - I didn't realize these were supposed to be different.
> You should probably define compat_ioctl to return an int as well
> so that it becomes possible to use the same function for both eventually.
The existing tty layer compat_ioctl is defined to return long; is that
also wrong?
> Then again, we can also drop the file argument, which is entirely unused
> in all the usb-serial ioctls.
I'm not sure it's worth the effort; if some future usb serial ioctl
needs the argument, we'd end up changing every existing driver back. I
assume there are some serial devices for which the file is relevant
during ioctl.
> Maybe the best way for now is to make the new compat_ioctl be
> int compat_ioctl(struct tty_struct, unsigned int cmd, unsigned long arg);
> and leave the old ioctl as it is. When we get around to pushing the
> BKL down into ->ioctl, we can change the prototype at the same time
> to warn potential out-of-tree drivers.
Let's figure out what the right compat_ioctl interface is first and
worry about fixing the existing ioctl interface later.
--
keith.packard@intel.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-11-27 18:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 8:29 [PATCH] usb/serial: Add compat_ioctl pass-through Keith Packard
2008-11-27 8:29 ` [PATCH] usb/serial/cp2101: Add support for cp2103 GPIO pins Keith Packard
2008-11-27 10:58 ` Alan Cox
2008-11-27 18:20 ` Keith Packard
2008-11-27 18:41 ` Greg KH
2008-11-28 1:31 ` Keith Packard
2008-12-03 7:12 ` Greg KH
2008-12-03 8:11 ` Keith Packard
2008-11-27 14:31 ` [PATCH] usb/serial: Add compat_ioctl pass-through Arnd Bergmann
2008-11-27 18:27 ` Keith Packard [this message]
2008-11-28 11:43 ` Arnd Bergmann
2008-11-28 14:03 ` Alan Cox
2008-11-28 15:42 ` Arnd Bergmann
2008-11-28 22:28 ` Keith Packard
2008-11-28 22:33 ` Alan Cox
2008-11-29 1:02 ` Keith Packard
2008-11-29 1:10 ` Alan Cox
2008-11-29 1:23 ` Arjan van de Ven
2008-11-29 1:37 ` Alan Cox
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=1227810424.4277.55.camel@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=arnd@arndb.de \
--cc=gregkh@suse.de \
--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