From: Thomas Gleixner <tglx@linutronix.de>
To: Yang Honggang <eagle.rtlinux@gmail.com>
Cc: linux-rt-users@vger.kernel.org, rtlinux@163.com, 杨民强 <mqyoung@gmail.com>
Subject: Re: file system bug
Date: Mon, 4 Jun 2012 15:26:25 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1206041525150.3086@ionos> (raw)
In-Reply-To: <4FC77A06.2090706@gmail.com>
On Thu, 31 May 2012, Yang Honggang wrote:
> Hello,
>
> There is no rt patch from 2.6.34 until 3.0. It said that the reason is that
> there
> is a serious file system bug which will cause file corruption.
> And the bug is fixed by Thomas until the version 2.6.38??
>
> It will be very grateful if some detail information about this bug can be
> given.
The bug was only visible with the changes RT did to that
code. Mainline papered over it somehow, but I forgot the details by
now.
next prev parent reply other threads:[~2012-06-04 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 14:02 file system bug Yang Honggang
2012-06-04 13:26 ` Thomas Gleixner [this message]
2012-06-05 7:35 ` Yang Honggang
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.02.1206041525150.3086@ionos \
--to=tglx@linutronix.de \
--cc=eagle.rtlinux@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=mqyoung@gmail.com \
--cc=rtlinux@163.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;
as well as URLs for NNTP newsgroup(s).