linux-kernel - Re: types for storing instruction pointers

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]

Date:	Sun, 7 Jun 2009 15:25:16 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Christoph Hellwig <hch@....de>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: types for storing instruction pointers


* Christoph Hellwig <hch@....de> wrote:

> Currently the _THIS_IP_ and _RET_IP_ macros aded for lockdep but 
> now available from kernel.org case the instruction pointer to an 
> unsigned long.  But the %pf/%pF format for printing them want a 
> pointer of some sort.  That's a pretty nasty situation for tracers 
> - can we standardize on one type for it?

Yes but what's the practical problem exactly? Could you cite an 
example?

Thanks,

	Ingo
--
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/