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  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 4 Jun 2009 21:13:50 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Mike Frysinger <vapier.adi@...il.com>
Cc:	tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
	jason.wessel@...driver.com, kgdb-bugreport@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kgdbts: unify/generalize gdb breakpoint adjustment

On Fri, 5 Jun 2009 00:00:22 -0400 Mike Frysinger <vapier.adi@...il.com> wrote:

> your version after all requires every arch to copy & paste this crap:
> static inline unsigned long instruction_pointer(struct pt_regs *regs)
> {
>     return regs->ip;
> }
> static inline void instruction_pointer_set(struct pt_regs *regs,
> unsigned long val)
> {
>     regs->ip = val;
> }
> 
> and then actual usage turns into:
> instruction_pointer_set(regs, instruction_pointer(regs) + foo);
> 
> whereas mine is two lines:
> #define instruction_pointer(regs) ((regs)->ip)
> instruction_pointer(regs) += val;

The aim isn't really to reduce the amount of typing one needs to do. 
Let's get things right, and if getting it right involves more typing
then so be it.


If it really worries you then you could do

#define GET_IP(regs)	((regs)->ip)
#include <asm/generic/instruction_pointer.h>

and

static inline unsigned long instruction_pointer(struct pt_regs *regs)
{
	return GET_IP(regs);
}

static inline void instruction_pointer_set(struct pt_regs *regs,
					unsigned long val)
{
	GET_IP(regs) = val;
}

Note that GET_IP() is all-caps, which says "this is a macro".

But I don't think it's worth the ickyness, unless we also incorporate
kernel_stack_pointer(), frame_pointer(), user_stack_pointer() and
perhaps the _set() versions of those also.



Do we know how to implement instruction_pointer_set() on ia64, btw?
--
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