Re: [tip:perf/urgent] perf symbols: Handle /proc/sys/kernel/kptr_restrict
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:perf/urgent] perf symbols: Handle /proc/sys/kernel/kptr_restrict
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 27 May 2011 08:46:42 -0700
- Cc: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, paulus@xxxxxxxxx, hpa@xxxxxxxxx, mingo@xxxxxxxxxx, eranian@xxxxxxxxxx, tzanussi@xxxxxxxxx, penberg@xxxxxxxxxxxxxx, efault@xxxxxx, peterz@xxxxxxxxxxxxx, davej@xxxxxxxxxx, davem@xxxxxxxxxxxxx, fweisbec@xxxxxxxxx, kees.cook@xxxxxxxxxxxxx, tglx@xxxxxxxxxxxxx, linux-tip-commits@xxxxxxxxxxxxxxx
- In-reply-to: <20110527083554.GA21386@xxxxxxx>
On Fri, May 27, 2011 at 1:35 AM, Ingo Molnar <mingo@xxxxxxx> wrote:
>
> I think the biggest problem is that it is yelling at us even when i'm
> root - and root can access all the pointer values just fine:
Instead of looking at the kptr_restrict file, please just look at the
addresses in the kallsyms file, and if they are all zero, you know
that it's not a usable kallsyms file (and you can pretty much assume
that it's due to kptr_restrict).
So I think the whole symbol__read_kptr_restrict() thing is just
pointless. Don't do it.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]
