From: Linus Torvalds <torvalds@linux-foundation.org>
To: Timothy Shimmin <tes@sgi.com>
Cc: lkml@vger.kernel.org, xfs-oss <xfs@oss.sgi.com>,
Andrew Morton <akpm@linux-foundation.org>,
stable@kernel.org, toei.rei@stargazer.at
Subject: Re: [PATCH] fix barrier fail detection in XFS
Date: Fri, 10 Oct 2008 11:04:31 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0810101103520.3503@nehalem.linux-foundation.org> (raw)
In-Reply-To: <48EEF60D.4020602@sgi.com>
On Fri, 10 Oct 2008, Timothy Shimmin wrote:
>
> This is an important fix posted by Christoph Hellwig today.
> Without this fix, XFS can turn off barriers when we wrap our ondisk log.
> Which could lead to corruption after unclean unmounts/shutdowns
> on machines without a persistent write cache etc.
Ok, it clearly didn't make it into 2.6.27. I assume it it should be marked
for stable?
Linus
next prev parent reply other threads:[~2008-10-10 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 6:28 [PATCH] fix barrier fail detection in XFS Timothy Shimmin
2008-10-10 18:04 ` Linus Torvalds [this message]
2008-10-10 18:07 ` Linus Torvalds
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=alpine.LFD.2.00.0810101103520.3503@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=lkml@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tes@sgi.com \
--cc=toei.rei@stargazer.at \
--cc=xfs@oss.sgi.com \
/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