From: David Miller <davem@davemloft.net>
To: wangchen@cn.fujitsu.com
Cc: kaber@trash.net, netdev@vger.kernel.org
Subject: Re: v2: [PATCH 2/3] netdevice: Fix promiscuity and allmulti overflow
Date: Tue, 17 Jun 2008 21:54:02 -0700 (PDT) [thread overview]
Message-ID: <20080617.215402.169100957.davem@davemloft.net> (raw)
In-Reply-To: <48586A04.6040800@cn.fujitsu.com>
From: Wang Chen <wangchen@cn.fujitsu.com>
Date: Wed, 18 Jun 2008 09:51:00 +0800
> Patrick McHardy said the following on 2008-6-17 20:59:
> >> + printk(KERN_ERR "%s: promiscuity touches roof, "
> >> + "set promiscuity failed, promiscuity feature "
> >> + "of device will be broken.\n", dev->name);
> >> + return -EOVERFLOW;
> >> + }
> >> + }
> >
> > Assuming the caller does proper error handling, that printk is
> > not true.
> >
>
> Yes.
> But currently, no caller handling this, and I think even if I make
> some callers to handle this, but there maybe some callers and their
> callers do not want to handle error condition.
> So I need a KERN_WARNING here.
> If some day, all of the caller handle the error properly, we can
> remove this printk.
>
> Here is v3:
Patrick, ACK?
next prev parent reply other threads:[~2008-06-18 4:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 9:15 RFC: [PATCH 2/3] netdevice: Fix promiscuity and allmulti overflow Wang Chen
2008-06-16 9:38 ` Patrick McHardy
2008-06-16 9:51 ` Wang Chen
2008-06-16 10:04 ` Patrick McHardy
2008-06-16 15:05 ` v2: " Wang Chen
2008-06-17 12:59 ` Patrick McHardy
2008-06-18 1:51 ` Wang Chen
2008-06-18 4:54 ` David Miller [this message]
2008-06-18 8:44 ` Patrick McHardy
2008-06-18 8:49 ` David Miller
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=20080617.215402.169100957.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=wangchen@cn.fujitsu.com \
/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).