linux-kernel - Re: [patch] printk: add KERN

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:	Thu, 4 Oct 2007 13:43:20 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	w@....eu, apw@...dowen.org, linux-kernel@...r.kernel.org
Subject: Re: [patch] printk: add KERN_CONT annotation

On Tue, 2 Oct 2007 07:18:52 +0200
Ingo Molnar <mingo@...e.hu> wrote:

> 
> printk: add the KERN_CONT annotation (which is empty string but via 
> which checkpatch.pl can notice that the lacking KERN_ level is fine). 
> This useful for multiple calls of hand-crafted printk output done by 
> early debug code or similar.
> 

I like it.  Sort of self-documenting notation.

> 
> Index: linux/include/linux/kernel.h
> ===================================================================
> --- linux.orig/include/linux/kernel.h
> +++ linux/include/linux/kernel.h
> @@ -61,6 +61,13 @@ extern const char linux_proc_banner[];
>  #define	KERN_INFO	"<6>"	/* informational			*/
>  #define	KERN_DEBUG	"<7>"	/* debug-level messages			*/
>  
> +/*
> + * Annotation for a "continued" line of log printout (only done after a
> + * line that had no enclosing \n). Only to be used by core/arch code
> + * during early bootup (a continued line is not SMP-safe otherwise).
> + */
> +#define	KERN_CONT	""
> +
>  extern int console_printk[];
>  
>  #define console_loglevel (console_printk[0])
> Index: linux/kernel/sched.c

I get rejects from the sched.c hunk and that's your stuff anwyay, so I
dropped that bit.

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