From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Lord <kernel@teksavvy.com>
Cc: Tejun Heo <tj@kernel.org>, Robert Hancock <hancockrwd@gmail.com>,
bl0 <bl0-052@playker.info>,
linux-ide@vger.kernel.org, linux-pci@vger.kernel.org,
Jeff Garzik <jeff@garzik.org>
Subject: Re: sata_sil data corruption, possible workarounds
Date: Mon, 14 Jan 2013 12:58:55 -0500 [thread overview]
Message-ID: <50F4475F.9000509@pobox.com> (raw)
In-Reply-To: <50F0199D.4090502@teksavvy.com>
On 01/11/2013 08:54 AM, Mark Lord wrote:
> 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.
Module options appear in sysfs anyway.
If the issue continues to be seen, a knob to enable an ugly solution is
better than nothing, from the user's perspective.
Jeff
next prev parent reply other threads:[~2013-01-14 17:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-15 8:02 sata_sil data corruption, possible workarounds bl0
2012-12-15 21:55 ` Robert Hancock
2012-12-16 12:21 ` bl0
2012-12-17 5:44 ` Robert Hancock
2012-12-18 15:23 ` bl0
2012-12-19 3:44 ` Robert Hancock
2012-12-20 8:54 ` bl0
2013-01-07 4:11 ` Robert Hancock
2013-01-08 12:25 ` bl0
2012-12-24 14:37 ` bl0
2013-01-09 4:48 ` Robert Hancock
2013-01-09 19:17 ` Tejun Heo
2013-01-11 10:28 ` bl0
2013-01-11 13:53 ` Mark Lord
2013-01-11 13:54 ` Mark Lord
2013-01-14 17:58 ` Jeff Garzik [this message]
2013-01-15 7:44 ` bl0
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50F4475F.9000509@pobox.com \
--to=jgarzik@pobox.com \
--cc=bl0-052@playker.info \
--cc=hancockrwd@gmail.com \
--cc=jeff@garzik.org \
--cc=kernel@teksavvy.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox