linux-kernel - Re: [PATCH] Don't export scsi kernel variables in userspace headers.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090727082623.GA18747@merkur.ravnborg.org>
Date:	Mon, 27 Jul 2009 10:26:23 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	linux-scsi@...r.kernel.org
Subject: Re: [PATCH] Don't export scsi kernel variables in userspace
	headers.

On Mon, Jul 27, 2009 at 03:44:18AM -0400, Christoph Hellwig wrote:
> On Fri, Jul 24, 2009 at 10:10:26PM -0400, Dave Jones wrote:
> > Found with make headers_check
> > 
> > /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
> 
> The headers shouldn't be exported at all because scsi/ headers are
> exported from glibc.
Where does glibc get these headers from?

If glibc have their own private copy then the headers should indeed be exported
so we avoid such mess.

	Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/