From: Florin Malita <fmalita@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: jeff@garzik.org, dcbw@redhat.com, linville@tuxdriver.com,
marcelo@kvack.org, linville@redhat.com, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] libertas: skb dereferenced after netif_rx
Date: Mon, 21 May 2007 10:51:38 -0400 [thread overview]
Message-ID: <4651B1FA.3010201@gmail.com> (raw)
In-Reply-To: <20070520.003832.59470116.davem@davemloft.net>
David Miller wrote:
> From: Jeff Garzik <jeff@garzik.org>
> Date: Sat, 19 May 2007 21:47:00 -0400
>
>> According to the implementation, netif_rx() can fail.
>>
>
> It doesn't exactly "fail", but it does give return values
> which indicate RX congestion.
>
Assuming you're referring to NET_RX_CN_*, this doesn't seem to be the
case anymore: it appears netif_rx can only return NET_RX_SUCCESS or
NET_RX_DROP.
The congestion level constants are hardly used at all - if they are
left-overs, would it make sense ripping them out completely?
Either way I believe the following should be OK:
Remove inaccurate netif_rx() return value comments.
Signed-off-by: Florin Malita <fmalita@gmail.com>
---
dev.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/net/core/dev.c b/net/core/dev.c
index f2b6111..79f5d90 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -1628,9 +1628,6 @@ DEFINE_PER_CPU(struct netif_rx_stats, netdev_rx_stat) = { 0, };
*
* return values:
* NET_RX_SUCCESS (no congestion)
- * NET_RX_CN_LOW (low congestion)
- * NET_RX_CN_MOD (moderate congestion)
- * NET_RX_CN_HIGH (high congestion)
* NET_RX_DROP (packet was dropped)
*
*/
WARNING: multiple messages have this Message-ID (diff)
From: Florin Malita <fmalita-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org,
dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org,
marcelo-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
linville-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] libertas: skb dereferenced after netif_rx
Date: Mon, 21 May 2007 10:51:38 -0400 [thread overview]
Message-ID: <4651B1FA.3010201@gmail.com> (raw)
In-Reply-To: <20070520.003832.59470116.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
David Miller wrote:
> From: Jeff Garzik <jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
> Date: Sat, 19 May 2007 21:47:00 -0400
>
>> According to the implementation, netif_rx() can fail.
>>
>
> It doesn't exactly "fail", but it does give return values
> which indicate RX congestion.
>
Assuming you're referring to NET_RX_CN_*, this doesn't seem to be the
case anymore: it appears netif_rx can only return NET_RX_SUCCESS or
NET_RX_DROP.
The congestion level constants are hardly used at all - if they are
left-overs, would it make sense ripping them out completely?
Either way I believe the following should be OK:
Remove inaccurate netif_rx() return value comments.
Signed-off-by: Florin Malita <fmalita-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
---
dev.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/net/core/dev.c b/net/core/dev.c
index f2b6111..79f5d90 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -1628,9 +1628,6 @@ DEFINE_PER_CPU(struct netif_rx_stats, netdev_rx_stat) = { 0, };
*
* return values:
* NET_RX_SUCCESS (no congestion)
- * NET_RX_CN_LOW (low congestion)
- * NET_RX_CN_MOD (moderate congestion)
- * NET_RX_CN_HIGH (high congestion)
* NET_RX_DROP (packet was dropped)
*
*/
next prev parent reply other threads:[~2007-05-21 14:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 21:01 [PATCH] libertas: skb dereferenced after netif_rx Florin Malita
2007-05-18 18:09 ` John W. Linville
2007-05-18 18:09 ` John W. Linville
2007-05-18 20:04 ` Florin Malita
2007-05-18 20:04 ` Florin Malita
2007-05-19 5:23 ` Stephen Hemminger
2007-05-19 5:23 ` Stephen Hemminger
2007-05-19 5:37 ` Jeff Garzik
2007-05-19 5:37 ` Jeff Garzik
2007-05-20 0:56 ` Dan Williams
2007-05-20 1:47 ` Jeff Garzik
2007-05-20 5:20 ` Stephen Hemminger
2007-05-20 5:20 ` Stephen Hemminger
2007-05-20 6:36 ` Jeff Garzik
2007-05-20 7:38 ` David Miller
2007-05-20 7:38 ` David Miller
2007-05-21 14:51 ` Florin Malita [this message]
2007-05-21 14:51 ` Florin Malita
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=4651B1FA.3010201@gmail.com \
--to=fmalita@gmail.com \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=jeff@garzik.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@redhat.com \
--cc=linville@tuxdriver.com \
--cc=marcelo@kvack.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.