[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0905061845540.12391@blonde.anvils>
Date: Wed, 6 May 2009 18:54:22 +0100 (BST)
From: Hugh Dickins <hugh@...itas.com>
To: Chris Wright <chrisw@...hat.com>
cc: Izik Eidus <ieidus@...hat.com>, Rik van Riel <riel@...hat.com>,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
aarcange@...hat.com, alan@...rguk.ukuu.org.uk, device@...ana.org,
linux-mm@...ck.org, nickpiggin@...oo.com.au
Subject: Re: [PATCH 3/6] ksm: change the KSM_REMOVE_MEMORY_REGION ioctl.
On Wed, 6 May 2009, Chris Wright wrote:
> * Hugh Dickins (hugh@...itas.com) wrote:
> >
> > Is the phrase "covert channel" going to come up somehow?
>
> There's two (still hand wavy) conerns I see there. First is the security
> implication: timing writes to see cow and guess the shared data for
> another apps VM_LOCKED region,
Mmm, yes, there's fun to be had there; though I don't see it as having
anything to do with VM_LOCKED, beyond that the paranoid have reason to
place their most anxious data in VM_LOCKED areas.
I'm thinking of an app which prepares pages full of scurrilous rumour,
then waits around looking at its /proc/self/smaps to see if anyone else
is writing stories like that!
> second is just plain old complaints of
> those rt latency sensitive apps that somehow have VM_LOCKED|VM_MERGE
> and complain of COW fault time, probably just "don't do that".
Right. There are sensitive sites which ought not to configure such
merging on; but I don't think we should disallow merging locked.
Hugh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists