linux-kernel - Re: [PATCHv2 0/4] scsi: export and clean up 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: <20090929124347.GA11375@infradead.org>
Date:	Tue, 29 Sep 2009 08:43:47 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	"Michael S. Tsirkin" <mst@...hat.com>
Cc:	James Bottomley <James.Bottomley@...senPartnership.com>,
	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
	Boaz Harrosh <bharrosh@...asas.com>,
	Sam Ravnborg <sam@...nborg.org>,
	Ulrich Drepper <drepper@...hat.com>
Subject: Re: [PATCHv2 0/4] scsi: export and clean up headers

On Tue, Sep 29, 2009 at 12:33:53PM +0200, Michael S. Tsirkin wrote:
> This implements a minor cleanup of exported scsi headers,
> and adds export of headers that are de-facto used by userspace.
> The patches are on top of 2.6.32-rc1.
> Can these be queued for 2.6.32?
> Thanks.

Before we do anything in this area we need to find an agreement who
owns /usr/include/scsi/ .  Right now that's glibc, and if we want to
change it to the kernel headers we need to find a transition agreement
with the glibc maintainer (aka mostly Uli).

And even then it's quite questionable if the kernel should provide
scsi.h as it's mostly protocol defintions, not actually a kernel
interface.

--
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/