From: Martin Michlmayr <tbm@cyrius.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Hugh Dickins <hugh@veritas.com>,
linux-kernel@vger.kernel.org, debian-kernel@lists.debian.org,
linux-mm <linux-mm@kvack.org>, David Miller <davem@davemloft.net>
Subject: Re: Recent mm changes leading to filesystem corruption?
Date: Sat, 16 Dec 2006 21:23:46 +0000 [thread overview]
Message-ID: <20061216212346.GA4426@unjust.cyrius.com> (raw)
In-Reply-To: <1166302516.10372.5.camel@twins>
* Peter Zijlstra <a.p.zijlstra@chello.nl> [2006-12-16 21:55]:
> What is not clear from all these reports is what architectures this is
> seen on. I suspect some of them are i686, which together with the
> explicit mention of ARM make it a cross platform issue.
Problems have been seen at least on x86, x86_64 and arm.
--
Martin Michlmayr
tbm@cyrius.com
WARNING: multiple messages have this Message-ID (diff)
From: Martin Michlmayr <tbm@cyrius.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Hugh Dickins <hugh@veritas.com>,
linux-kernel@vger.kernel.org, debian-kernel@lists.debian.org,
linux-mm <linux-mm@kvack.org>, David Miller <davem@davemloft.net>
Subject: Re: Recent mm changes leading to filesystem corruption?
Date: Sat, 16 Dec 2006 21:23:46 +0000 [thread overview]
Message-ID: <20061216212346.GA4426@unjust.cyrius.com> (raw)
In-Reply-To: <1166302516.10372.5.camel@twins>
* Peter Zijlstra <a.p.zijlstra@chello.nl> [2006-12-16 21:55]:
> What is not clear from all these reports is what architectures this is
> seen on. I suspect some of them are i686, which together with the
> explicit mention of ARM make it a cross platform issue.
Problems have been seen at least on x86, x86_64 and arm.
--
Martin Michlmayr
tbm@cyrius.com
--
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 21:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 15:50 Recent mm changes leading to filesystem corruption? Martin Michlmayr
2006-12-16 18:20 ` Hugh Dickins
2006-12-16 18:20 ` Hugh Dickins
2006-12-16 18:44 ` Martin Michlmayr
2006-12-16 18:44 ` Martin Michlmayr
2006-12-16 19:07 ` Hugh Dickins
2006-12-16 19:07 ` Hugh Dickins
2006-12-16 20:55 ` Peter Zijlstra
2006-12-16 20:55 ` Peter Zijlstra
2006-12-16 21:23 ` Martin Michlmayr [this message]
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=20061216212346.GA4426@unjust.cyrius.com \
--to=tbm@cyrius.com \
--cc=a.p.zijlstra@chello.nl \
--cc=davem@davemloft.net \
--cc=debian-kernel@lists.debian.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.