From: David Miller <davem@davemloft.net>
To: rmk@arm.linux.org.uk
Cc: buytenh@wantstofly.org, James.Bottomley@steeleye.com,
linux-arch@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [CFT] read+shared mmap write+read data corruption
Date: Tue, 29 May 2007 03:26:03 -0700 (PDT) [thread overview]
Message-ID: <20070529.032603.59469832.davem@davemloft.net> (raw)
In-Reply-To: <20070529091252.GA4832@flint.arm.linux.org.uk>
From: Russell King <rmk@arm.linux.org.uk>
Date: Tue, 29 May 2007 10:12:52 +0100
> Could we have PG_arch_2 as bit 13 for this purpose, guaranteed to be
> cleared on page cache page allocation? IOW, same rules as far as the
> non-arch code is concerned as PG_arch_1.
I don't think there will be much objection to adding one more arch bit
:-)
next prev parent reply other threads:[~2007-05-29 10:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-27 10:49 [CFT] read+shared mmap write+read data corruption Russell King
2007-05-27 14:16 ` James Bottomley
2007-05-27 22:25 ` Lennert Buytenhek
2007-05-27 23:06 ` David Miller
2007-05-27 23:05 ` David Miller
2007-05-28 0:31 ` James Bottomley
2007-05-28 12:44 ` Lennert Buytenhek
2007-05-29 5:35 ` David Miller
2007-05-29 9:12 ` Russell King
2007-05-29 10:26 ` David Miller [this message]
2007-05-27 22:24 ` Lennert Buytenhek
2007-05-28 0:00 ` James Bottomley
2007-05-28 10:05 ` Russell King
2007-05-28 14:17 ` James Bottomley
2007-05-28 14:39 ` Lennert Buytenhek
2007-05-29 3:06 ` James Bottomley
2007-05-29 3:15 ` Lennert Buytenhek
2007-05-29 14:32 ` James Bottomley
2007-05-29 17:13 ` Russell King
2007-05-29 5:58 ` David Miller
2007-05-28 15:04 ` Russell King
2007-05-29 15:42 ` Lennert Buytenhek
2007-05-28 12:33 ` Lennert Buytenhek
2007-05-28 14:22 ` James Bottomley
2007-05-28 12:38 ` Lennert Buytenhek
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=20070529.032603.59469832.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=buytenh@wantstofly.org \
--cc=linux-arch@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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