[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090728110028.31fa9a6f@lxorguk.ukuu.org.uk>
Date: Tue, 28 Jul 2009 11:00:28 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Andi Kleen <andi@...stfloor.org>
Cc: James Morris <jmorris@...ei.org>,
James Carter <jwcart2@...ho.nsa.gov>,
Eric Paris <eparis@...hat.com>, linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org, selinux@...ho.nsa.gov,
Stephen Smalley <sds@...ho.nsa.gov>, spender@...ecurity.net,
Daniel J Walsh <dwalsh@...hat.com>, cl@...ux-foundation.org,
Arjan van de Ven <arjan@...radead.org>, kees@...flux.net,
Chad Sellers <csellers@...sys.com>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
mingo@...e.hu
Subject: Re: mmap_min_addr and your local LSM (ok, just SELinux)
On Tue, 28 Jul 2009 11:21:29 +0200
Andi Kleen <andi@...stfloor.org> wrote:
> Alan Cox <alan@...rguk.ukuu.org.uk> writes:
>
> > A dumb question perhaps, but while addling my brain over the tty layer I
> > was wondering if for the specific case of jump through NULL (which seems
> > to be the most common but by no means only problem case that gets
> > exploited) is there any reason we can't set a default breakpoint for
>
> You mean a hardware breakpoint? Hardware break points are a precious
> scarce resource. The people who rely on them would be likely
> unhappy if you take one way from them.
They are a tiny minority and could always turn such protection off.
--
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