linux-kernel - Re: reinstate dm target local ioctl support

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: <20160128140022.GA15941@lst.de>
Date:	Thu, 28 Jan 2016 15:00:22 +0100
From:	Christoph Hellwig <hch@....de>
To:	Andy Whitcroft <apw@...onical.com>
Cc:	Alasdair Kergon <agk@...hat.com>,
	Mike Snitzer <snitzer@...hat.com>,
	Christoph Hellwig <hch@....de>, mohan_srinivasan@...oo.com,
	dm-devel@...hat.com, Neil Brown <neilb@...e.com>,
	linux-raid@...r.kernel.org, linux-kernel@...r.kernel.org,
	Tim Gardner <tim.gardner@...onical.com>
Subject: Re: reinstate dm target local ioctl support

On Thu, Jan 28, 2016 at 01:50:19PM +0000, Andy Whitcroft wrote:
> However this also removed the possibility of a dm target having target
> specific ioctls.  Currently this is not used by any in-tree targets but
> was utilised by the flashcache out-of-tree module.
> 
> How would we feel about carrying something like the patch below in
> mainline to allow for such target local ioctls.

Bad.  Because a) targets shouldn't have their own ioctls and b) your out
of tree modules are your problem, don't burden us wіth upstream
workarounds for it.