Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755165Ab2ECMlE (ORCPT ); Thu, 3 May 2012 08:41:04 -0400 Received: from ironport-out.teksavvy.com ([206.248.143.162]:23697 "EHLO ironport-out.teksavvy.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754983Ab2ECMlC (ORCPT ); Thu, 3 May 2012 08:41:02 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuEBACxOgk8Y9geI/2dsb2JhbAANNoVzsCSGLAEBAQEDI1UBEAsOCgICBRYLAgIJAwIBAgFFBg0BBwEBtCSKGIEvjhOBGASpJQ X-IronPort-AV: E=Sophos;i="4.75,391,1330923600"; d="scan'208";a="178177001" Message-ID: <4FA27CDB.2080103@teksavvy.com> Date: Thu, 03 May 2012 08:40:59 -0400 From: Mark Lord User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Paolo Bonzini CC: Alan Cox , Jan Kara , Jens Axboe , LKML , James Bottomley , linux-scsi@vger.kernel.org Subject: Re: [PATCH] scsi: Silence unnecessary warnings about ioctl to partition References: <1335953452-10460-1-git-send-email-jack@suse.cz> <4FA1092E.9090603@redhat.com> <20120502115447.7dcc3a54@pyramind.ukuu.org.uk> <4FA11454.2010103@redhat.com> <20120502121208.3c19a9bc@pyramind.ukuu.org.uk> <4FA11963.3040007@redhat.com> <4FA18D33.3060607@teksavvy.com> <4FA23809.2090905@redhat.com> In-Reply-To: <4FA23809.2090905@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 991 Lines: 26 On 12-05-03 03:47 AM, Paolo Bonzini wrote: > Il 02/05/2012 21:38, Mark Lord ha scritto: >>>> >>>> Indeed, RHEL doesn't have the warning at all and blocks all ioctls >>>> including SG_IO (and in the past six months nobody has complained that >>>> something stopped working for them). Never said the patch is perfect... >> hdparm. >> > > Breaking "hdparm --write-sector /dev/sda1"? I call it a security fix. No, that would plain stupid on both our parts. :) The --write-sector flag is allowed only for non-partitions by hdparm itself. But other flags commonly used by distros at boot time seem to be triggering the current in-kernel noise. Dunno which flags, I'm just ignoring them and waiting for the noise message to get reverted. Cheers -- 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/