From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ironport2-out.teksavvy.com ([206.248.154.182]:13505 "EHLO ironport2-out.teksavvy.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751113Ab3AKNyj (ORCPT ); Fri, 11 Jan 2013 08:54:39 -0500 Message-ID: <50F0199D.4090502@teksavvy.com> Date: Fri, 11 Jan 2013 08:54:37 -0500 From: Mark Lord MIME-Version: 1.0 To: Tejun Heo CC: Robert Hancock , bl0 , linux-ide@vger.kernel.org, linux-pci@vger.kernel.org, Jeff Garzik Subject: Re: sata_sil data corruption, possible workarounds References: <50CCF1E0.9070804@gmail.com> <50CEB13B.9010100@gmail.com> <50ECF6AB.30007@gmail.com> <20130109191753.GQ3926@htj.dyndns.org> <50F01968.4030309@teksavvy.com> In-Reply-To: <50F01968.4030309@teksavvy.com> Content-Type: text/plain; charset=UTF-8 Sender: linux-pci-owner@vger.kernel.org List-ID: On 13-01-11 08:53 AM, Mark Lord wrote: > On 13-01-09 02:17 PM, Tejun Heo wrote: >> >> Having a module option is easy and can be helpful for the very rare >> cases where the admin is aware of the issue, but, in general, it >> doesn't really help that much. > > How about a sysfs attribute, rather than a boot option? NAK that idea.. a boot-time module flag is the best way.