| 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
| ||
|
Message-ID: <20130522091449.GD18810@twins.programming.kicks-ass.net> Date: Wed, 22 May 2013 11:14:49 +0200 From: Peter Zijlstra <peterz@...radead.org> To: Sasha Levin <sasha.levin@...cle.com> Cc: torvalds@...ux-foundation.org, mingo@...nel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v4 2/9] liblockdep: Wrap kernel/lockdep.c to allow usage from userspace On Wed, May 15, 2013 at 11:15:34PM -0400, Sasha Levin wrote: > kernel/lockdep.c deals with validating locking scenarios for > various architectures supported by the kernel. There isn't > anything kernel specific going on in lockdep, and when we > compare userspace to other architectures that don't have to deal > with irqs such as s390, they become all too similar. > > We wrap kernel/lockdep.c and include/linux/lockdep.h with > several headers which allow us to build and use lockdep from > userspace. We don't touch the kernel code itself which means > that any work done on lockdep in the kernel will automatically > benefit userspace lockdep as well! > > + > +#ifndef CALLER_ADDR0 > +#define _THIS_IP_ CALLER_ADDR0 > +#define CALLER_ADDR0 ((unsigned long)__builtin_return_address(0)) > +#endif Why are you making _THIS_IP_ equal to _RET_IP_ ? -- 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/
Powered by blists - more mailing lists