linux-kernel - Re: [patch] get rid of "cut here" from bug output

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, 17 Jun 2010 14:36:37 +0200
From:	Borislav Petkov <bp@...64.org>
To:	Dan Carpenter <error27@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [patch] get rid of "cut here" from bug output

From: Dan Carpenter <error27@...il.com>
Date: Thu, Jun 17, 2010 at 02:21:56PM +0200

> It's annoying to have chunks of dmesg output instead just the whole
> output.  A lot of times the very interesting information is before
> the bug happens.
> 
> Signed-off-by: Dan Carpenter <error27@...il.com>
> 
> diff --git a/kernel/panic.c b/kernel/panic.c
> index 3b16cd9..2db532a 100644
> --- a/kernel/panic.c
> +++ b/kernel/panic.c
> @@ -373,7 +373,7 @@ static void warn_slowpath_common(const char *file, int line, void *caller,
>  {
>  	const char *board;
>  
> -	printk(KERN_WARNING "------------[ cut here ]------------\n");
> +	printk(KERN_WARNING "-----[ paste whole dmesg to bugzilla ]-----\n");

Good idea, we end up requesting the whole dmesg most of the time anyway.
However not all bugs are reported through bugzilla, and, frankly
bugzilla is kinda sucky when it comes down to communicating with the bug
reporter. How about the more generic "send whole dmesg when reporting"
instead?

-- 
Regards/Gruss,
Boris.

Operating Systems Research Center
Advanced Micro Devices, Inc.
--
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/