From: Hugh Dickins <hugh@veritas.com>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>, Jan Kara <jack@suse.cz>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
debian-kernel@lists.debian.org
Subject: Re: Recent mm changes leading to filesystem corruption?
Date: Sat, 16 Dec 2006 19:07:05 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0612161903270.25272@blonde.wat.veritas.com> (raw)
In-Reply-To: <20061216184450.GA21129@deprecation.cyrius.com>
On Sat, 16 Dec 2006, Martin Michlmayr wrote:
> * Hugh Dickins <hugh@veritas.com> [2006-12-16 18:20]:
> > Very disturbing. I'm not aware of any problem with them, and we
> > surely wouldn't have released 2.6.19 with any known-corrupting patches
> > in. There's some doubts about 2.6.19 itself in the links below: were
> > it not for those, I'd suspect a mismerge of the pieces into 2.6.18,
> > perhaps a hidden dependency on something else. I'll ponder a little,
> > but let's CC linux-mm in case someone there has an idea.
>
> Do you think http://article.gmane.org/gmane.linux.kernel/473710 might
> be related?
Sounds like it. Let's CC Jan Kara on your other thread,
he seems to have delved into it a little.
Hugh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-12-16 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061216155044.GA14681@deprecation.cyrius.com>
2006-12-16 18:20 ` Hugh Dickins
2006-12-16 18:44 ` Martin Michlmayr
2006-12-16 19:07 ` Hugh Dickins [this message]
2006-12-16 20:55 ` Peter Zijlstra
2006-12-16 21:23 ` Martin Michlmayr
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=Pine.LNX.4.64.0612161903270.25272@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=a.p.zijlstra@chello.nl \
--cc=debian-kernel@lists.debian.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tbm@cyrius.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