From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: PING^7 (was Re: [PATCH v2 00/14] Corrections and customization of the SG_IO command whitelist (CVE-2012-4542)) Date: Sat, 25 May 2013 01:27:44 -0400 Message-ID: <20130525052744.GA25186@infradead.org> References: <20130522193009.GA23845@mtj.dyndns.org> <519D360D.4050309@redhat.com> <20130522221737.GA12339@mtj.dyndns.org> <519DC926.4000106@redhat.com> <20130523090222.GA26592@mtj.dyndns.org> <519DE5AD.7080303@redhat.com> <20130524014405.GB16882@mtj.dyndns.org> <519F12FF.6090809@redhat.com> <1369456502.5008.5.camel@dabdike> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1369456502.5008.5.camel@dabdike> Sender: linux-kernel-owner@vger.kernel.org To: James Bottomley Cc: Tejun Heo , Paolo Bonzini , Jens Axboe , lkml , "linux-scsi@vger.kernel.org" List-Id: linux-scsi@vger.kernel.org On Fri, May 24, 2013 at 09:35:02PM -0700, James Bottomley wrote: > I'll go along with this. I'm also wondering what the problem would be > if we just allowed all commands on either CAP_SYS_RAWIO or opening the > device for write, so we just defer to the filesystem permissions and > restricted read only opens to the basic all device opcodes. I've been out of this area for a bit, but the problem used to be that you could send destructive commands to a partition. The right fix for that would be to not allow SG_IO on partitions at all, just wondering if anything would be broken by this.