From: Michael Tokarev <mjt@tls.msk.ru>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git patches] libata fixes for 3.7
Date: Wed, 03 Oct 2012 09:23:42 +0400 [thread overview]
Message-ID: <506BCBDE.2020402@msgid.tls.msk.ru> (raw)
In-Reply-To: <506B47AB.9020506@pobox.com>
On 02.10.2012 23:59, Jeff Garzik wrote:
> On 10/02/2012 03:44 PM, Michael Tokarev wrote:
>> On 02.10.2012 23:40, Jeff Garzik wrote:
>>
>>> Minor libata updates, nothing notable.
>>>
>>> 1) Apply -- and then revert -- the FUA feature. Caused
>>> disk corruption in linux-next, proving it cannot be turned on by
>>> default.
>>
>> Any details on that? Disk corruprion is rather a nasty
>> side-effect indeed.
>
> One thread with reports is
>
> Storage related regression in linux-next 20120824
Eg, https://lkml.org/lkml/2012/8/27/66 (two reports).
Thank you!
/mjt
prev parent reply other threads:[~2012-10-03 5:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 19:40 [git patches] libata fixes for 3.7 Jeff Garzik
2012-10-02 19:44 ` Michael Tokarev
2012-10-02 19:59 ` Jeff Garzik
2012-10-03 5:23 ` Michael Tokarev [this message]
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=506BCBDE.2020402@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=akpm@linux-foundation.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.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