Re: [BUG] perf: bogus correlation of kernel symbols
[Posted May 17, 2011 by corbet]
| From: |
| David Miller <davem-AT-davemloft.net> |
| To: |
| torvalds-AT-linux-foundation.org |
| Subject: |
| Re: [BUG] perf: bogus correlation of kernel symbols |
| Date: |
| Thu, 12 May 2011 16:43:19 -0400 (EDT) |
| Message-ID: |
| <20110512.164319.1770509419224900253.davem@davemloft.net> |
| Cc: |
| eranian-AT-google.com, acme-AT-redhat.com, linux-kernel-AT-vger.kernel.org,
mingo-AT-elte.hu |
| Archive-link: |
| Article, Thread
|
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Thu, 12 May 2011 13:31:37 -0700
> That said, I have considered just reverting the thing that makes
> kptr_restrict be 1 by default. I do like the security implications of
> restricting visibility into kernel pointers, but I also think that
> security rules that make the system less usable are dubious. So I
> dunno.
We don't have any firewalling or SELINUX rules installed by default,
even if those features are enabled in the kernel. Userspace asks for
it.
Many people would claim that use of such things are "essential" these
days.
I don't see a good reason to handle kptr_restrict any differently.
(
Log in to post comments)