linux-kernel - Re: [PATCH 3/9] printk: add CON

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]

Message-ID: <20130301145805.GC30938@pd.tnic>
Date:	Fri, 1 Mar 2013 15:58:06 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Jeff Moyer <jmoyer@...hat.com>
Cc:	Joern Engel <joern@...fs.org>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 3/9] printk: add CON_ALLDATA console flag

On Fri, Mar 01, 2013 at 09:52:27AM -0500, Jeff Moyer wrote:
> > For consoles like netconsole and blockconsole the loglevel filtering
> > really doesn't make any sense.  If a line gets printed at all, please
> > send it down to that console, no questions asked.
> 
> Could you please explain this a bit further?  Why wouldn't you want to
> allow the admin to filter log messages to the block or network console?
> This doesn't make a whole lot of sense to me, and in fact could cause
> problems for netconsole now that you're potentially sending a ton more
> traffic over the wire.

Let's reverse the question: why would the admin ever want to filter
messages to debugging consoles like netconsole or blockconsole?

When running a debugging session, you generally want to see *all*
messages.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/