From: Pavel Roskin <proski@gnu.org>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Christoph Hellwig <hch@lst.de>,
jgarzik@pobox.com, hermes@gibson.dropbear.id.au,
netdev@oss.sgi.com
Subject: Re: [PATCH 11/12] orinoco: monitor mode support
Date: Sun, 22 May 2005 23:40:39 -0400 [thread overview]
Message-ID: <1116819639.726.6.camel@dv> (raw)
In-Reply-To: <20050517212217.GB12936@electric-eye.fr.zoreil.com>
Hello, Francois!
On Tue, 2005-05-17 at 23:22 +0200, Francois Romieu wrote:
> I am not fond of unneeded/hidden state variable. What about:
>
> + /* sanity check the length */
> + if (datalen > IEEE80211_DATA_LEN + 12) {
> + printk(KERN_DEBUG "%s: oversized monitor frame, "
> + "data length = %d\n", dev->name, datalen);
> + err = -EIO;
> + goto drop;
> ^^^^^^^^^^ -> let's replace by 'goto update_stats;'
> And turn:
> + drop:
> + stats->rx_errors++;
> + stats->rx_dropped++;
>
> into:
>
> + drop:
> + dev_kfree_skb_irq(skb);
> + update_stats:
> + stats->rx_errors++;
> + stats->rx_dropped++;
>
> This way 'goto drop' really drops and the code does not issue a 'goto drop'
> when it actually want to update the stats.
I agree. Closer look shows that orinoco needs a complete overhaul of
stats in the rx path. I'm going to fix it in CVS, and I'll post the
patch to netdev after it receives some testing.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2005-05-23 3:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 15:31 [PATCH 11/12] orinoco: monitor mode support Christoph Hellwig
2005-05-14 17:39 ` Francois Romieu
2005-05-17 19:43 ` Pavel Roskin
2005-05-17 21:22 ` Francois Romieu
2005-05-23 3:40 ` Pavel Roskin [this message]
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=1116819639.726.6.camel@dv \
--to=proski@gnu.org \
--cc=hch@lst.de \
--cc=hermes@gibson.dropbear.id.au \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.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).