From: Hugh Dickins <hugh@veritas.com>
To: "David S. Miller" <davem@redhat.com>
Cc: willy@debian.org, <James.Bottomley@SteelEye.com>,
<linux-kernel@vger.kernel.org>,
<parisc-linux@lists.parisc-linux.org>, <drepper@redhat.com>
Subject: Re: [parisc-linux] Re: Problems with kernel mmap (failing tst-mmap-eofsync in glibc on parisc)
Date: Fri, 22 Aug 2003 19:34:41 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0308221926060.2200-100000@localhost.localdomain> (raw)
In-Reply-To: <20030822110144.5f7b83c5.davem@redhat.com>
On Fri, 22 Aug 2003, David S. Miller wrote:
>
> So the proposed patch looks bogus to me.
And to me. If VM_SHARED is set, then __vma_link_file puts the vma on
on i_mmap_shared. If VM_SHARED is not set, it puts the vma on i_mmap.
flush_dcache_page treats i_mmap_shared and i_mmap lists equally.
Might the problem be in parisc's __flush_dcache_page,
which only examines i_mmap_shared?
Though it's odd, I'm not keen on changing do_mmap_pgoff's usage of
VM_SHARED in a hurry: it's worked like that for years, and other
things (I forget) depend on it.
Hugh
next prev parent reply other threads:[~2003-08-22 18:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-22 14:40 Problems with kernel mmap (failing tst-mmap-eofsync in glibc on parisc) James Bottomley
2003-08-22 16:14 ` David S. Miller
2003-08-22 16:34 ` [parisc-linux] " Matthew Wilcox
2003-08-22 16:39 ` David S. Miller
2003-08-22 17:41 ` Matthew Wilcox
2003-08-22 17:36 ` David S. Miller
2003-08-22 18:01 ` David S. Miller
2003-08-22 18:34 ` Hugh Dickins [this message]
2003-08-22 18:31 ` David S. Miller
2003-08-22 18:56 ` James Bottomley
2003-08-22 19:19 ` David S. Miller
2003-08-22 22:27 ` James Bottomley
2003-08-22 22:41 ` David S. Miller
2003-08-23 1:09 ` James Bottomley
2003-08-23 7:22 ` Hugh Dickins
2003-08-23 15:59 ` James Bottomley
2003-08-23 21:44 ` David S. Miller
2003-08-23 21:43 ` David S. Miller
2003-08-23 22:21 ` James Bottomley
2003-08-23 22:51 ` David S. Miller
2003-08-23 23:01 ` James Bottomley
2003-08-23 22:53 ` David S. Miller
2003-08-23 23:11 ` James Bottomley
2003-08-24 0:22 ` David S. Miller
[not found] ` <1061702282.1992.1153.camel@mulgrave>
[not found] ` <20030823222300.4695a0c4.davem@redhat.com>
2003-08-24 16:54 ` James Bottomley
2003-08-22 18:41 ` James Bottomley
2003-08-22 19:02 ` Hugh Dickins
2003-08-22 19:09 ` Randolph Chung
2003-08-22 16:42 ` Russell King
2003-08-22 16:39 ` David S. Miller
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.44.0308221926060.2200-100000@localhost.localdomain \
--to=hugh@veritas.com \
--cc=James.Bottomley@SteelEye.com \
--cc=davem@redhat.com \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=willy@debian.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 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).