linux-kernel - Re: [PATCH 1/7] Add a new debug function to kernel.h

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] [day] [month] [year] [list]

Message-Id: <1181536497.3423.10.camel@shark.themaw.net>
Date:	Mon, 11 Jun 2007 12:34:57 +0800
From:	Ian Kent <raven@...maw.net>
To:	Jack Stone <jack@...keye.stone.uk.eu.org>
Cc:	linux-kernel@...r.kernel.org, hpa@...or.com
Subject: Re: [PATCH 1/7] Add a new debug function to kernel.h

On Sat, 2007-06-09 at 09:06 +0100, Jack Stone wrote:
> This patch adds a new macro to print to KERN_ERR initially for ncp but
> others may want to use it

Yes, the patch set takes away local control of debug printing that I may
need to turn on for the module without re-compiling the kernel.

> 
> Signed-off-by: Jack Stone <jack@...keye.stone.uk.eu.org>
> ---
> Index: linux/include/linux/kernel.h
> ===================================================================
> --- linux.orig/include/linux/kernel.h
> +++ linux/include/linux/kernel.h
> @@ -228,11 +228,18 @@ extern void print_hex_dump(const char *l
>  /* If you are writing a driver, please use dev_dbg instead */
>  #define pr_debug(fmt,arg...) \
>  	printk(KERN_DEBUG fmt,##arg)
> +#define pr_err(fmt,arg...) \
> +	printk(KERN_ERR fmt,##arg)
>  #else
>  static inline int __attribute__ ((format (printf, 1, 2)))
> pr_debug(const char * fmt, ...)
>  {
>  	return 0;
>  }
> +
> +static inline int __attribute__ ((format (printf, 1, 2))) pr_err(const
> char * fmt, ...)
> +{
> +	return 0;
> +}
>  #endif
> 
>  #define pr_info(fmt,arg...) \
> 
> 

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