From: Andrew Morton <akpm@osdl.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: andrea@suse.de, nickpiggin@yahoo.com.au, linux-kernel@vger.kernel.org
Subject: Re: smp race fix between invalidate_inode_pages* and do_no_page
Date: Wed, 11 Jan 2006 13:05:33 -0800 [thread overview]
Message-ID: <20060111130533.6f23685b.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0601111949070.6448@goblin.wat.veritas.com>
Hugh Dickins <hugh@veritas.com> wrote:
>
> But I do not know what guarantees invalidate_inode_pages2 is supposed
> to give. As soon as you emerge from iipages2, its work could be undone:
yup. It cannot become a hard guarantee unless we add some new really big
locks.
So it can be fooled by silly or poorly-designed apps. What we're aiming
for here is predictable behaviour for sanely-implemented applications and
refusal to oops or to expose insecure data for poorly-designed ones or
exploits.
next prev parent reply other threads:[~2006-01-11 21:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-13 19:37 smp race fix between invalidate_inode_pages* and do_no_page Andrea Arcangeli
2005-12-13 21:02 ` Andrew Morton
2005-12-13 21:14 ` Andrea Arcangeli
2005-12-16 13:51 ` Andrea Arcangeli
2006-01-10 6:24 ` Andrea Arcangeli
2006-01-10 6:48 ` Andrea Arcangeli
2006-01-11 4:08 ` Nick Piggin
2006-01-11 8:23 ` Andrea Arcangeli
2006-01-11 8:51 ` Andrew Morton
2006-01-11 9:02 ` Andrea Arcangeli
2006-01-11 9:06 ` Andrew Morton
2006-01-11 9:13 ` Andrea Arcangeli
2006-01-11 20:49 ` Hugh Dickins
2006-01-11 21:05 ` Andrew Morton [this message]
2006-01-13 7:35 ` Nick Piggin
2006-01-13 7:47 ` Andrew Morton
2006-01-13 10:37 ` Nick Piggin
2006-03-31 12:36 ` Andrea Arcangeli
2006-04-02 5:17 ` Nick Piggin
2006-04-02 5:21 ` Andrew Morton
2006-04-07 19:18 ` Hugh Dickins
2006-01-11 9:39 ` Nick Piggin
2006-01-11 9:34 ` Nick Piggin
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=20060111130533.6f23685b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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).