From: Arnd Bergmann <arnd.bergmann@de.ibm.com>
To: Petr Vandrovec <petr@vandrovec.name>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCH] ncpfs: move ioctl32 code to fs/ncpfs/ioctl.c
Date: Thu, 27 Jul 2006 07:45:41 +0200 [thread overview]
Message-ID: <200607270745.42622.arnd.bergmann@de.ibm.com> (raw)
In-Reply-To: <44C83480.6000102@vandrovec.name>
On Thursday 27 July 2006 05:35, Petr Vandrovec wrote:
> Yes, tomorrow (on amd64).
No need to hurry, I was sitting on my patch for more than a year now ;-)
> Although I understand that this code is correct, what about removing this second
> #ifdef ? gcc should realize it anyway that without CONFIG_COMPAT defined cmd
> must be equal to NCP_IOC_GETPRIVATEDATA, and having empty "else" variant is IMHO
> just asking for troubles.
That was what I did first, but unfortunately we don't define compat_caddr_t when
CONFIG_COMPAT is disabled, so it would reference an invalid data structure.
> Or what about
>
> #ifdef CONFIG_COMPAT
> if (cmd == NCP_IOC_GETPRIVATEDATA_32) {
> struct ...
> } else
> #endif
> if (copy_to_user(argp, &user, sizeof(user)))
> return -EFAULT;
Yes, that should be clearer than my approach.
Arnd <><
next prev parent reply other threads:[~2006-07-27 5:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 8:51 [patch/rfc] s390: get rid of own uid16 compat system calls Heiko Carstens
2006-07-27 1:03 ` Arnd Bergmann
2006-07-27 1:08 ` reference: ncpfs: move ioctl32 code to fs/ncpfs/ioctl.c Arnd Bergmann
2006-07-27 2:53 ` Arnd Bergmann
2006-07-27 1:09 ` reference: smbfs: simplify compat_ioctl handling Arnd Bergmann
2006-07-27 2:56 ` [PATCH] ncpfs: move ioctl32 code to fs/ncpfs/ioctl.c Arnd Bergmann
2006-07-27 3:35 ` Petr Vandrovec
2006-07-27 5:45 ` Arnd Bergmann [this message]
2006-07-28 2:15 ` Petr Vandrovec
2006-07-28 3:38 ` Arnd Bergmann
2006-07-27 6:06 ` [patch/rfc] s390: get rid of own uid16 compat system calls Heiko Carstens
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=200607270745.42622.arnd.bergmann@de.ibm.com \
--to=arnd.bergmann@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=petr@vandrovec.name \
--cc=schwidefsky@de.ibm.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