From: James Smart <James.Smart@Emulex.Com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
Olaf Hering <olh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Sam Ravnborg <sam@ravnborg.org>,
Benny Halevy <bhalevy@panasas.com>,
LKML <linux-kernel@vger.kernel.org>,
"Smart, James" <James.Smart@Emulex.Com>
Subject: Re: [PATCH] SCSI: userspace cannot use scsi_command_size_tbl, COMMAND_SIZE and scsi_device_type
Date: Sun, 28 Jun 2009 10:32:32 -0400 [thread overview]
Message-ID: <4A477F00.70305@emulex.com> (raw)
In-Reply-To: <4A47222B.5020702@panasas.com>
Sorry folks -- the nuance of the clibrary having it's own version of a
kernel header for distros was completely unknown to me.
Christoph mentioned this to me last week, with the recommendation to
back out the patch and move the other headers that were exprted into
include/linux - thus nothing in include/scsi gets export. No Problem.
and I'll do so shortly.
How does a lowly contributor track these kind of nuances ?
-- james s
Boaz Harrosh wrote:
> On 06/27/2009 08:05 PM, Jaswinder Singh Rajput wrote:
>
>> userspace cannot use scsi_command_size_tbl, COMMAND_SIZE
>> and scsi_device_type defined in kernel
>>
>> fix the following 'make headers_check' warnings:
>>
>> usr/include/scsi/scsi.h:159: userspace cannot call function or variable defined in the kernel
>> usr/include/scsi/scsi.h:285: userspace cannot call function or variable defined in the kernel
>>
>> Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
>>
>
> include/scsi/scsi.h was always provided by glibc and was never exported from Kernel.
> It was only recently added to include/scsi/Kbuild. (In this merge window, was never released)
> (see: [9e4f5e29] [SCSI] FC Pass Thru support)
>
> Two questions.
> 1. Are we sure this will work. Is the Header fully compatible with glibc's header.
> 2. What will this do to distor's package managers having the same file in two packages?
> Don't we need a followup patch sent to glibc to remove that Header from there?
>
> James Smart
> What is the new definitions needed in user-mode in scsi.h that is not available in glibc's
> supplied header?
>
> (For reference see this patch from 2007: [e629a7dd] do not export /usr/include/scsi in make headers_install)
>
> Boaz
>
next prev parent reply other threads:[~2009-06-28 14:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 17:05 [PATCH] SCSI: userspace cannot use scsi_command_size_tbl, COMMAND_SIZE and scsi_device_type Jaswinder Singh Rajput
2009-06-27 17:27 ` James Bottomley
2009-06-27 17:56 ` Jaswinder Singh Rajput
2009-06-27 18:28 ` Matthew Wilcox
2009-06-27 18:40 ` Jaswinder Singh Rajput
2009-06-28 13:52 ` James Bottomley
2009-06-28 14:09 ` Boaz Harrosh
2009-07-02 14:41 ` Jaswinder Singh Rajput
2009-06-28 7:56 ` Boaz Harrosh
2009-06-28 14:32 ` James Smart [this message]
2009-06-28 14:44 ` James Bottomley
2009-06-28 16:00 ` Boaz Harrosh
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=4A477F00.70305@emulex.com \
--to=james.smart@emulex.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bhalevy@panasas.com \
--cc=bharrosh@panasas.com \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
--cc=sam@ravnborg.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