From: Bart Van Assche <bvanassche@acm.org>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: -Wswitch Clang warnings in drivers/scsi
Date: Fri, 19 Oct 2018 06:55:29 -0700 [thread overview]
Message-ID: <da70bb3c-3474-7fa5-032c-2abad01deb9d@acm.org> (raw)
In-Reply-To: <20181019065104.GA27170@flashbox>
On 10/18/18 11:51 PM, Nathan Chancellor wrote:
> On Mon, Oct 08, 2018 at 11:47:09AM -0700, Bart Van Assche wrote:
>> From the user space header <sys/ioctl.h>:
>>
>> extern int ioctl (int __fd, unsigned long int __request, ...) __THROW;
>>
>> From the kernel header <linux/fs.h>:
>>
>> long (*unlocked_ioctl) (struct file *, unsigned int, unsigned long);
>> long (*compat_ioctl) (struct file *, unsigned int, unsigned long);
>>
>> Why has the second argument been declared as "unsigned long" in the glibc
>> headers and as "unsigned int" in the kernel headers? That's not clear to me.
>>
>> Bart.
>>
>
> Hi Bart,
>
> Sorry it took me so long to reply, somehow this email got lost in my
> inbox...
>
> Unfortuntely, I am unsure why there is that discrepency between the
> headers. I tried to do some research but I didn't come up with much.
>
> However, I did test changing the type of ioctl/compat_ioctl's cmd
> parameter to 'unsigned int' and came up with the following diff (rather
> large so sharing via a gist instead of pasting here):
>
> https://gist.github.com/nathanchance/8febc92735f4228574cb0464520f0f6f
>
> I'll obviously draft up a proper commit message before formally sending
> but I can address any major concerns before that happens. I checked
> every single ioctl for a negative value and there aren't any so I think
> this change makes sense to fix this warning.
Hi Nathan,
Since that change makes the SCSI code more consistent with the rest of
the Linux kernel, I'm in favor of making that change.
Bart.
prev parent reply other threads:[~2018-10-19 13:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 18:30 Nathan Chancellor
2018-10-04 18:34 ` Bart Van Assche
2018-10-04 18:45 ` Nathan Chancellor
2018-10-04 21:16 ` Nick Desaulniers
2018-10-05 6:57 ` Nathan Chancellor
2018-10-08 18:12 ` Nick Desaulniers
2018-10-08 18:47 ` Bart Van Assche
2018-10-19 6:51 ` Nathan Chancellor
2018-10-19 13:55 ` Bart Van Assche [this message]
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=da70bb3c-3474-7fa5-032c-2abad01deb9d@acm.org \
--to=bvanassche@acm.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.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
all inboxes | Powered by JetHome®