| 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
| ||
|
Message-Id: <201211051626.29317.arnd@arndb.de> Date: Mon, 5 Nov 2012 16:26:29 +0000 From: Arnd Bergmann <arnd@...db.de> To: Julia Lawall <julia.lawall@...6.fr> Cc: walter harms <wharms@....de>, kernel-janitors@...r.kernel.org, "Greg Kroah-Hartman" <gregkh@...uxfoundation.org>, Jason Wessel <jason.wessel@...driver.com>, kgdb-bugreport@...ts.sourceforge.net, linux-kernel@...r.kernel.org Subject: Re: [PATCH] drivers/misc/kgdbts.c: remove eprintk On Sunday 04 November 2012, Julia Lawall wrote: > > > > I don't see yet where that KERN_WARNING gets added. Looking at > > warn_slowpath_common, there are two or three lines that get printed at > > KERN_WARNING level, followed by the format that got passed into WARN(), > > which may or may not include a printk level, but I don't see one getting > > added. > > OK, I agree. There are lots of KERN_WARNINGs, but not on the string that > was passed in. Still, maybe it is not so good to pass a KERN_XXX for some > other XXX to WARN. Given that most users don't pass anything here, and that those that do pass something are somewhat inconsistent, could we make the messages always get printed at KERN_WARNING level from WARN(), and kill off the instances that already pass a level? Arnd -- 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