* Kees Cook <keesc...@chromium.org> wrote:
> On Mon, Jan 27, 2014 at 9:20 AM, Richard Weinberger <rich...@nod.at> wrote:
> > Am 27.01.2014 18:05, schrieb Kees Cook:
> >> I would argue that decoding a non-panic oops on a running system is
> >> entirely possible as-is, since the offset can be found from
> >> /proc/kallsyms as root. It was the dead system that needed the offset
> >> exported: via text in the panic, or via an ELF note in a core.
> >
> > The problem is that you have to pickup information from two sources.
> > As a kernel developer users/customers often show you a backtrace (oops or
> > panic)
> > and want you do find the problem.
> > They barley manage it copy&paste the topmost full trace from dmesg or
> > /var/log/messages.
> > If I have to ask them a bit later to tell me the offset from /proc/kallsyms
> > or something else
> > I'm lost. Mostly because they have already rebooted the box...
>
> As long as I can turn it off, I'd be happy. :)
> /proc/sys/kernel/kaslr_in_oops or something?
Yeah, as long as it decodes by default.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
