mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>
To: Pan Bian <bianpan2016@163.com>, "David S. Miller" <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] amd-xgbe: set skb to NULL after freeing it
Date: Wed, 28 Nov 2018 14:23:48 +0000	[thread overview]
Message-ID: <49bcee7c-9c8e-33af-4cea-6f76c6f00349@amd.com> (raw)
In-Reply-To: <1543395975-25339-1-git-send-email-bianpan2016@163.com>

On 11/28/2018 03:06 AM, Pan Bian wrote:
> The buffer skb is freed via dev_kfree_skb in a loop. After freeing skb, 
> the value of packet_count is updated via packet_count++. If packet_count
> happens to equal the upper bound budget, the loop will be broken and skb 
> may be assigned to rdata->state.skb. Resulting that rdata->state.skb may

Except that rdata->state.skb is only assigned if we have received
something and it is (!last || context_next).  If error is ever set,
then we read descriptors as long as (!last || context_next).  Also,
packet->errors can only be set for the last packet which implies no
following context descriptors.  So rdata->state.skb can never be set
with the "bad" skb value.

The only way I can see this occurring is if a context descriptor is
indicated (context_next) along with packet->errors. Are you actually
seeing an error/crash where this is occurring?  If so, then the fix
should be to goto read_again if context_next is set because we want
to remove the context descriptor in this case and not save the state.

Thanks,
Tom

> point to a freed memory chunk. To fix this, the patch sets skb to NULL 
> after dev_kfree_skb(skb).
> 
> Signed-off-by: Pan Bian <bianpan2016@163.com>
> ---
> V2: correct the commit log
> ---
>  drivers/net/ethernet/amd/xgbe/xgbe-drv.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/net/ethernet/amd/xgbe/xgbe-drv.c b/drivers/net/ethernet/amd/xgbe/xgbe-drv.c
> index 0cc911f..ac6b82d 100644
> --- a/drivers/net/ethernet/amd/xgbe/xgbe-drv.c
> +++ b/drivers/net/ethernet/amd/xgbe/xgbe-drv.c
> @@ -2754,6 +2754,7 @@ static int xgbe_rx_poll(struct xgbe_channel *channel, int budget)
>  				netif_err(pdata, rx_err, netdev,
>  					  "error in received packet\n");
>  			dev_kfree_skb(skb);
> +			skb = NULL;
>  			goto next_packet;
>  		}
>  
> @@ -2806,6 +2807,7 @@ static int xgbe_rx_poll(struct xgbe_channel *channel, int budget)
>  			netif_err(pdata, rx_err, netdev,
>  				  "packet length exceeds configured MTU\n");
>  			dev_kfree_skb(skb);
> +			skb = NULL;
>  			goto next_packet;
>  		}
>  
> 

      reply	other threads:[~2018-11-28 14:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28  9:06 Pan Bian
2018-11-28 14:23 ` Lendacky, Thomas [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=49bcee7c-9c8e-33af-4cea-6f76c6f00349@amd.com \
    --to=thomas.lendacky@amd.com \
    --cc=bianpan2016@163.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®