From: David Miller <davem@davemloft.net>
To: yuehaibing@huawei.com
Cc: f.fainelli@gmail.com, grygorii.strashko@ti.com, w-kwok2@ti.com,
m-karicheri2@ti.com, lukas@wunner.de, bgolaszewski@baylibre.com,
ivan.khoronzhuk@linaro.org, dan.carpenter@oracle.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH net-next] net: ti: fix return type of ndo_start_xmit function
Date: Wed, 26 Sep 2018 10:17:33 -0700 (PDT) [thread overview]
Message-ID: <20180926.101733.2070254569725987062.davem@davemloft.net> (raw)
In-Reply-To: <20180926090951.25544-1-yuehaibing@huawei.com>
From: YueHaibing <yuehaibing@huawei.com>
Date: Wed, 26 Sep 2018 17:09:51 +0800
> @@ -1290,7 +1291,7 @@ static int netcp_ndo_start_xmit(struct sk_buff *skb, struct net_device *ndev)
> dev_warn(netcp->ndev_dev, "padding failed (%d), packet dropped\n",
> ret);
> tx_stats->tx_dropped++;
> - return ret;
> + return NETDEV_TX_BUSY;
> }
> skb->len = NETCP_MIN_PACKET_SIZE;
> }
> @@ -1298,7 +1299,6 @@ static int netcp_ndo_start_xmit(struct sk_buff *skb, struct net_device *ndev)
> desc = netcp_tx_map_skb(skb, netcp);
> if (unlikely(!desc)) {
> netif_stop_subqueue(ndev, subqueue);
> - ret = -ENOBUFS;
> goto drop;
> }
>
> @@ -1319,7 +1319,7 @@ static int netcp_ndo_start_xmit(struct sk_buff *skb, struct net_device *ndev)
> if (desc)
> netcp_free_tx_desc_chain(netcp, desc, sizeof(*desc));
> dev_kfree_skb(skb);
> - return ret;
> + return NETDEV_TX_BUSY;
> }
These conversions are not correct.
If the driver frees the SKB you must not return NETDEV_TX_BUSY.
NETDEV_TX_BUSY tells the caller that the driver could not process the
packet and that it should reqeueu up the SKB and try again later when
there is more TX queue room.
next prev parent reply other threads:[~2018-09-26 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 9:09 [PATCH net-next] net: ti: fix return type of ndo_start_xmit function YueHaibing
2018-09-26 17:17 ` David Miller [this message]
2018-09-26 20:36 ` Grygorii Strashko
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=20180926.101733.2070254569725987062.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bgolaszewski@baylibre.com \
--cc=dan.carpenter@oracle.com \
--cc=f.fainelli@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=ivan.khoronzhuk@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=m-karicheri2@ti.com \
--cc=netdev@vger.kernel.org \
--cc=w-kwok2@ti.com \
--cc=yuehaibing@huawei.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