From: chas williams - CONTRACTOR <chas@cmf.nrl.navy.mil>
To: nick <xerofoify@gmail.com>, Guy Ellis <guy@traverse.com.au>
Cc: linux-atm-general@lists.sourceforge.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: FIXME in solos-pci.c
Date: Thu, 4 Dec 2014 09:05:47 -0500 [thread overview]
Message-ID: <20141204090547.21fedeb9@thirdoffive.cmf.nrl.navy.mil> (raw)
In-Reply-To: <547FDBF6.5020008@gmail.com>
The last I heard on this topic was from Guy Ellis,
From: Guy Ellis <guy@traverse.com.au>
To: linux-atm-general@lists.sourceforge.net
Subject: Re: [Linux-ATM-General] solos-pci.c: Fix me
Date: Tue, 22 Jul 2014 07:34:30 +1000
Hi Chas/Nick,
I think the FIXME is reminder to deal correctly with an unknown command.
At the moment an unknown command is treated as a PKT_COMMAND which is
incorrect.
I think the correct behaviour would be to ignore unknown commands and
just free the skb.
That said I doubt this condition ever occurs, which is probably why it
has been this way since day 1.
Nathan is on vacation at the moment, when he gets back in August I'll
ask him to tidy this up.
So perhaps, Guy could let us know if he had a chance for Nathan to
look at removing this FIXME.
On Wed, 03 Dec 2014 22:58:46 -0500
nick <xerofoify@gmail.com> wrote:
> Greetings Chas,
> I am wondering if there is any reason for the FIXME message in the below code. This is due to after reading the other parts of the function the code and logical seem similar and correct unless I am missing something about the hardware.
> Cheers Nick
> case PKT_COMMAND:
> default: /* FIXME: Not really, surely? */
> if (process_command(card, port, skb))
> break;
> spin_lock(&card->cli_queue_lock);
> if (skb_queue_len(&card->cli_queue[port]) > 10) {
> if (net_ratelimit())
> dev_warn(&card->dev->dev, "Dropping console response on port %d\n",
> port);
> dev_kfree_skb_any(skb);
> } else
> skb_queue_tail(&card->cli_queue[port], skb);
> spin_unlock(&card->cli_queue_lock);
> break;
> }
>
>
parent reply other threads:[~2014-12-04 14:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <547FDBF6.5020008@gmail.com>]
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=20141204090547.21fedeb9@thirdoffive.cmf.nrl.navy.mil \
--to=chas@cmf.nrl.navy.mil \
--cc=guy@traverse.com.au \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xerofoify@gmail.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