Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757928Ab2ECRgJ (ORCPT ); Thu, 3 May 2012 13:36:09 -0400 Received: from ironport-out.teksavvy.com ([206.248.143.162]:5309 "EHLO ironport-out.teksavvy.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753061Ab2ECRgI (ORCPT ); Thu, 3 May 2012 13:36:08 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuEBACxOgk8Y9geI/2dsb2JhbAANNoVzsCSGLAEBAQECASNVARALDgoCAgUWCwICCQMCAQIBRQYNAQcBAYgFrB+KGIEvjhOBGASpJQ X-IronPort-AV: E=Sophos;i="4.75,391,1330923600"; d="scan'208";a="178210421" Message-ID: <4FA2C205.3030801@teksavvy.com> Date: Thu, 03 May 2012 13:36:05 -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> <4FA27CDB.2080103@teksavvy.com> <4FA27E7C.6070802@redhat.com> In-Reply-To: <4FA27E7C.6070802@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: 1245 Lines: 31 On 12-05-03 08:47 AM, Paolo Bonzini wrote: > Il 03/05/2012 14:40, Mark Lord ha scritto: >>>> >>>> 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. > > Excuse my laziness--how does it check? I don't know if there's a feasible fool-proof method or not. But what hdparm does is look at the sector offset of the device. Partitions normally have a non-zero offset. >> 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. > > That's exactly the behavior I hoped to get when I added the warnings. > Or maybe not. :) What are the messages? > i.e. what ioctl do they complain about? As above: >> Dunno which flags, I'm just ignoring them and waiting >> for the noise message to get reverted. -- 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/