From: Andrea Arcangeli <andrea@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Matthew Vanecek <linuxguy@directlink.net>,
linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: Updates to /bin/bash
Date: Sat, 6 May 2000 15:15:44 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.21.0005060519310.2332-100000@alpha.random> (raw)
In-Reply-To: <14610.29880.728540.947675@charged.uio.no>
On Fri, 5 May 2000, Trond Myklebust wrote:
>NO. This behaviour is exactly what Andreas patch would break. New
My patch won't hurt the bash update as far I can tell.
In clean 2.2.15 and clean 2.3.99-pre7-pre6 you don't unmap the page from
the ptes, so if nfs doesn't keep to do the pageins from the inode pointed
by the nfsfilehandle, then you'll get a mixture anyway even if you drop
the mapped pages from the cache (and nfs probably can't keep do to the
pageins from the old file if somebody replaced bash on the real fs but in
the worst case nfs should notice that and it should abort the `bash`
execution and to never do the silent mixture).
New executed bash are not an issue since they will get a new inode present
on the server and so they won't risk to do the mixture.
All above thoughts assumes the admin correctly uses remove(2) to upgrade
bash (otherwise the mixture would happen also on top of ext2).
About the stability issue I looked some more and maybe the VM is not
subject to stability issues by dropping a mapped cache-page from the cache
(however the thing keeps to look not robust to me). Everything depends on
the page->index that have to be not clobbered after dropping the page from
the cache (while page->index is supposed to have a meaning only on
pagecache or swapcache).
Andrea
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-05-06 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-04 19:53 Mark_H_Johnson.RTS
2000-05-05 0:14 ` Matthew Vanecek
2000-05-05 7:14 ` Trond Myklebust
2000-05-06 13:15 ` Andrea Arcangeli [this message]
2000-05-06 17:02 ` Steve Dodd
2000-05-05 13:32 Mark_H_Johnson.RTS
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.21.0005060519310.2332-100000@alpha.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=linuxguy@directlink.net \
--cc=trond.myklebust@fys.uio.no \
/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