Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755467Ab2FOI4r (ORCPT ); Fri, 15 Jun 2012 04:56:47 -0400 Received: from cantor2.suse.de ([195.135.220.15]:57494 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752544Ab2FOI4p (ORCPT ); Fri, 15 Jun 2012 04:56:45 -0400 Date: Fri, 15 Jun 2012 10:46:44 +0200 From: Jan Kara To: Paolo Bonzini Cc: Jan Kara , Jens Axboe , LKML , James Bottomley , linux-scsi@vger.kernel.org Subject: Re: [PATCH] scsi: Silence unnecessary warnings about ioctl to partition Message-ID: <20120615084644.GA3479@quack.suse.cz> References: <1335953452-10460-1-git-send-email-jack@suse.cz> <4FDAEED4.20601@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FDAEED4.20601@redhat.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2280 Lines: 59 On Fri 15-06-12 10:14:12, Paolo Bonzini wrote: > Il 02/05/2012 12:10, Jan Kara ha scritto: > > Sometimes, warnings about ioctls to partition happen often enough that they > > form majority of the warnings in the kernel log and users complain. In some > > cases warnings are about ioctls such as SG_IO so it's not good to get rid of > > the warnings completely as they can ease debugging of userspace problems > > when ioctl is refused. > > > > Since I have seen warnings from lots of commands, including some proprietary > > userspace applications, I don't think disallowing the ioctls for processes > > with CAP_SYS_RAWIO will happen in the near future if ever. So lets just > > stop warning for processes with CAP_SYS_RAWIO for which ioctl is allowed. > > > > CC: Paolo Bonzini > > CC: Jens Axboe > > CC: James Bottomley > > CC: linux-scsi@vger.kernel.org > > Signed-off-by: Jan Kara > > --- > > block/scsi_ioctl.c | 5 ++++- > > 1 files changed, 4 insertions(+), 1 deletions(-) > > > > diff --git a/block/scsi_ioctl.c b/block/scsi_ioctl.c > > index 260fa80..9a87daa 100644 > > --- a/block/scsi_ioctl.c > > +++ b/block/scsi_ioctl.c > > @@ -721,11 +721,14 @@ int scsi_verify_blk_ioctl(struct block_device *bd, unsigned int cmd) > > break; > > } > > > > + if (capable(CAP_SYS_RAWIO)) > > + return 0; > > + > > /* In particular, rule out all resets and host-specific ioctls. */ > > printk_ratelimited(KERN_WARNING > > "%s: sending ioctl %x to a partition!\n", current->comm, cmd); > > > > - return capable(CAP_SYS_RAWIO) ? 0 : -ENOIOCTLCMD; > > + return -ENOIOCTLCMD; > > } > > EXPORT_SYMBOL(scsi_verify_blk_ioctl); > > > > > > Ping? Good that you bring this up :). I've asked the customer about whether they can find out the particular SG_IO ioctl Veritas issues but never heard back. So will we merge my patch? I remember you gave it reluctant ack once ;). Honza -- Jan Kara SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/