linux-kernel - Re: [PATCH] kexec: Add prefix "kexec" to output message

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: <20150923070121.GC4394@dhcp-129-160.nay.redhat.com>
Date:	Wed, 23 Sep 2015 15:01:21 +0800
From:	Dave Young <dyoung@...hat.com>
To:	Baoquan He <bhe@...hat.com>
Cc:	Minfei Huang <mhuang@...hat.com>, kexec@...ts.infradead.org,
	linux-kernel@...r.kernel.org,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	akpm@...ux-foundation.org, Minfei Huang <mnfhuang@...il.com>
Subject: Re: [PATCH] kexec: Add prefix "kexec" to output message

On 09/23/15 at 10:49am, Baoquan He wrote:
> On 09/23/15 at 09:37am, Dave Young wrote:
> > > > Hi, Dave.
> > > > 
> > > > How about removing all of the prefix "crashkernel" in kexec_core. Thus
> > > > we can be consistent with the output message prefix "kexec".
> > > 
> > > Ping, any comment is appreciate and helpful.
> > 
> > Remove "crashkernel" sounds not a proper way, it indicates crashkernel parsing
> > messages. I have no idea what is the best way but below modification sounds better to me:
> > 
> > kexec_core.c:
> > 
> > #define pr_fmt(fmt)        "[kexec_core] " fmt
> > Also remove below prefix "Kexec:"
> > pr_warn("Kexec: Memory allocation for saving cpu register states failed\n"); 
> > 
> > kexec.c:
> > #define pr_fmt(fmt)        "[kexec] " fmt
> > 
> > kexec_file.c:
> > #define pr_fmt(fmt)        "[kexec_file] " fmt
> 
> This is weird, user really don't need to know each file. I saw you added
> a new file kexec_internal.h and all three files includes it. Why not doing
> it there to make it the same as before?

I personally do not like add these prefix to a header file. One prefix for
a c file is better to me.

But rethinking about the prefix, looks like there's a lot of other components
using ":" so KBUILD_MODNAME ": "  should be fine.

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