linux-kernel - Re: PATCH] debug: add notifier chain debugging

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080825215555.2331f2cc@infradead.org>
Date:	Mon, 25 Aug 2008 21:55:55 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	"Tony Luck" <tony.luck@...el.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu
Subject: Re: PATCH] debug: add notifier chain debugging

On Mon, 25 Aug 2008 15:39:13 -0700
"Tony Luck" <tony.luck@...el.com> wrote:

> On Fri, Aug 15, 2008 at 3:29 PM, Arjan van de Ven
> <arjan@...radead.org> wrote:
> > +       if (!kernel_text_address((unsigned long)n->notifier_call)) {
> > +               WARN(1, "Invalid notifier registered!");
> > +               return 0;
> > +       }
> 
> This breaks on ia64 (and pa-risc I think) where function pointers
> don't point directly at the code, they point to a {code,data}
> structure which is itself located in data space, not text space.

is there a way to go to the actual address? I'm sure this is a bit more
common.... (like kallsyms!)


-- 
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/