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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20110726085721.GB2075@arm.com>
Date:	Tue, 26 Jul 2011 09:57:25 +0100
From:	Dave Martin <dave.martin@...aro.org>
To:	Stephen Boyd <sboyd@...eaurora.org>
Cc:	Randy Dunlap <rdunlap@...otime.net>,
	Russell King <linux@....linux.org.uk>,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-doc@...r.kernel.org
Subject: Re: [PATCH] Documentation: Document ARM's user_debug parameter

On Mon, Jul 25, 2011 at 02:29:24PM -0700, Randy Dunlap wrote:
> On Sun, 24 Jul 2011 18:15:14 -0700 Stephen Boyd wrote:
> 
> > Usually kernel parameters are documented in kernel-parameters.txt
> > but user_debug is only documented in the Kconfig. Document the
> > option and point to the Kconfig help text for more info.
> > 
> > Signed-off-by: Stephen Boyd <sboyd@...eaurora.org>
> > Cc: Russell King <linux@....linux.org.uk>
> 
> Is this a superset of 'print_fatal_signals'?
> 
> Applied, thanks.
> 
> > ---
> >  Documentation/kernel-parameters.txt |   10 ++++++++++
> >  1 files changed, 10 insertions(+), 0 deletions(-)
> > 
> > diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> > index aa47be7..8186adc 100644
> > --- a/Documentation/kernel-parameters.txt
> > +++ b/Documentation/kernel-parameters.txt
> > @@ -2612,6 +2612,16 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
> >  					medium is write-protected).
> >  			Example: quirks=0419:aaf5:rl,0421:0433:rc
> >  
> > +	user_debug=	[KNL,ARM]
> > +			Format: <int>
> > +			See arch/arm/Kconfig.debug help text.
> > +				 1 - undefined instruction events
> > +				 2 - system calls

linux$ git grep UDBG_SYSCALL -- arch/arm/
include/asm/system.h:#define UDBG_SYSCALL       (1 << 1)
kernel/traps.c: if (user_debug & UDBG_SYSCALL) {
kernel/traps.c: if (user_debug & UDBG_SYSCALL) {

Looking at kernel/traps.c, it looks like only undefined or obsolete
syscalls are logged.  It could be worth clarifying this in the wording,
both here and in arch/arm/Kconfig.debug.

Cheers
---Dave

> > +				 4 - invalid data aborts
> > +				 8 - SIGSEGV faults
> > +				16 - SIGBUS faults
> > +			Example: user_debug=31
> > +
> >  	userpte=
> >  			[X86] Flags controlling user PTE allocations.
> >  
> > -- 
> > Sent by an employee of the Qualcomm Innovation Center, Inc.
> > The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
> 
> ---
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ