netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "YOSHIFUJI Hideaki / _$B5HF#1QL@" <yoshfuji@linux-ipv6.org>
Cc: davem@redhat.com, netdev@oss.sgi.com, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH] NETDEBUG network triggerable messages in IPv6
Date: Fri, 9 Apr 2004 18:21:25 +0200	[thread overview]
Message-ID: <20040409182125.348fd6cd.ak@suse.de> (raw)
In-Reply-To: <20040410.010051.129465789.yoshfuji@linux-ipv6.org>

On Sat, 10 Apr 2004 01:00:51 +0900 (JST)
YOSHIFUJI Hideaki / _$B5HF#1QL@ <yoshfuji@linux-ipv6.org> wrote:

> In article <20040409174847.2f0b7e77.ak@suse.de> (at Fri, 9 Apr 2004 17:48:47 +0200), Andi Kleen <ak@suse.de> says:
> 
> > This wraps all potentially network triggerable printks in IPv6 with NETDEBUG.
> 
> I really do NOT like this. Please, please do not do this.

If you don't like it just keep NETDEBUG on. But for production systems being able 
to fill up logs from the network is not acceptable IMHO. Anyways default behaviour
does not change right now, it just allows to easily disable all this cruft for
people who want that.

-Andi

  reply	other threads:[~2004-04-09 16:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-09 15:48 [PATCH] NETDEBUG network triggerable messages in IPv6 Andi Kleen
2004-04-09 16:00 ` YOSHIFUJI Hideaki / 吉藤英明
2004-04-09 16:21   ` Andi Kleen [this message]
2004-04-09 17:18     ` YOSHIFUJI Hideaki / 吉藤英明
2004-04-09 17:31       ` Andi Kleen
2004-04-09 17:47         ` YOSHIFUJI Hideaki / 吉藤英明
2004-04-09 17:50           ` Andi Kleen
2004-04-09 18:09             ` YOSHIFUJI Hideaki / 吉藤英明
2004-04-09 18:24               ` Andi Kleen
2004-04-16 20:52         ` David S. Miller
2004-04-09 18:06     ` Nivedita Singhvi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040409182125.348fd6cd.ak@suse.de \
    --to=ak@suse.de \
    --cc=davem@redhat.com \
    --cc=netdev@oss.sgi.com \
    --cc=yoshfuji@linux-ipv6.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).