[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f11576a0905100539l1512170oc64f7aee2864e8d5@mail.gmail.com>
Date: Sun, 10 May 2009 21:39:58 +0900
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Wu Fengguang <fengguang.wu@...el.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
"hannes@...xchg.org" <hannes@...xchg.org>,
"riel@...hat.com" <riel@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tytso@....edu" <tytso@....edu>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"elladan@...imo.com" <elladan@...imo.com>,
"npiggin@...e.de" <npiggin@...e.de>,
"cl@...ux-foundation.org" <cl@...ux-foundation.org>,
"minchan.kim@...il.com" <minchan.kim@...il.com>
Subject: Re: [PATCH -mm] vmscan: make mapped executable pages the first class
citizen
>> > They always use mmap(PROT_READ | PROT_WRITE | PROT_EXEC) for anycase.
>> > Please google it. you can find various example.
>>
>> How widely is PROT_EXEC abused? Would you share some of your google results?
>
> That's a security bug right there and should be fixed regardless of our
> heuristics.
Yes, should be. but it's not security issue. it doesn't make any security hole.
Plus, this claim doesn't help to solve end-user problems.
I think the basic concept of the patch is right.
- executable mapping is important for good latency
- executable file is relatively small
The last problem is, The patch assume executable mappings is rare, but
it isn't guranteed.
How do we separate truth executable mapping and mis-used PROT_EXEC usage?
--
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