From: Aleksa Sarai <asarai@suse.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-alpha@vger.kernel.org,
"open list:RALINK MIPS ARCHITECTURE" <linux-mips@linux-mips.org>,
Parisc List <linux-parisc@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-sh@vger.kernel.org, sparclinux <sparclinux@vger.kernel.org>,
linux-xtensa@linux-xtensa.org,
linux-arch <linux-arch@vger.kernel.org>,
Christian Brauner <christian.brauner@ubuntu.com>,
Valentin Rothberg <vrothberg@suse.com>
Subject: Re: [PATCH v3 1/2] tty: add compat_ioctl callbacks
Date: Tue, 6 Jun 2017 21:05:06 +1000 [thread overview]
Message-ID: <6faa7b93-a355-f7ba-e5e9-12f2414ac695@suse.de> (raw)
In-Reply-To: <CAK8P3a3j4rB+iVX=a36csE6mX9iMRp14TS1UeePyFsjTKQyiZw@mail.gmail.com>
>> diff --git a/Makefile b/Makefile
>> index 470bd4d9513a..fb689286d83a 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -401,6 +401,7 @@ KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
>> -fno-strict-aliasing -fno-common \
>> -Werror-implicit-function-declaration \
>> -Wno-format-security \
>> + -Wno-error=int-in-bool-context \
>> -std=gnu89 $(call cc-option,-fno-PIE)
>
> This slipped in by accident I assume? It seems completely unrelated.
Yeah, I re-sent v4 with this removed immediately afterwards.
>
>> diff --git a/drivers/tty/pty.c b/drivers/tty/pty.c
>> index 65799575c666..2a6bd9ae3f8b 100644
>> --- a/drivers/tty/pty.c
>> +++ b/drivers/tty/pty.c
>> @@ -481,6 +481,16 @@ static int pty_bsd_ioctl(struct tty_struct *tty,
>> return -ENOIOCTLCMD;
>> }
>>
>> +static long pty_bsd_compat_ioctl(struct tty_struct *tty,
>> + unsigned int cmd, unsigned long arg)
>> +{
>> + /*
>> + * PTY ioctls don't require any special translation between 32-bit and
>> + * 64-bit userspace, they are already compatible.
>> + */
>> + return pty_bsd_ioctl(tty, cmd, arg);
>> +}
>> +
>
> This looks correct but unnecessary, you can simply point both
> function pointers to the same function:
They have different types, since they have different return types:
int (*ioctl)(struct tty_struct *tty,
unsigned int cmd, unsigned long arg);
long (*compat_ioctl)(struct tty_struct *tty,
unsigned int cmd, unsigned long arg);
If you like, I can change (*ioctl) to return longs as well, and then
change all of the call-sites (since unlocked_ioctl also returns long).
--
Aleksa Sarai
Software Engineer (Containers)
SUSE Linux GmbH
https://www.cyphar.com/
next prev parent reply other threads:[~2017-06-06 11:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 13:51 [PATCH v3 0/2] tty: add TIOCGPTPEER ioctl Aleksa Sarai
2017-06-03 13:51 ` [PATCH v3 1/2] tty: add compat_ioctl callbacks Aleksa Sarai
2017-06-03 14:13 ` Aleksa Sarai
2017-06-03 14:16 ` kbuild test robot
2017-06-03 14:31 ` kbuild test robot
2017-06-06 11:01 ` Arnd Bergmann
2017-06-06 11:05 ` Aleksa Sarai [this message]
2017-06-06 12:46 ` Arnd Bergmann
2017-06-03 13:51 ` [PATCH v3 2/2] tty: add TIOCGPTPEER ioctl Aleksa Sarai
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=6faa7b93-a355-f7ba-e5e9-12f2414ac695@suse.de \
--to=asarai@suse.de \
--cc=arnd@arndb.de \
--cc=christian.brauner@ubuntu.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sparclinux@vger.kernel.org \
--cc=vrothberg@suse.com \
/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