From: Steen Hegelund <steen.hegelund@microchip.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
<UNGLinuxDriver@microchip.com>, <netdev@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH net] net: sparx5: do not refer to skb after passing it on
Date: Wed, 2 Feb 2022 09:23:00 +0100 [thread overview]
Message-ID: <d55ed1f583c31df17e98300ca91996a2446f4523.camel@microchip.com> (raw)
In-Reply-To: <20220201200521.179857d7@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Hi Jacub,
Thanks for the feedback.
I will update according to your suggestions.
BR
Steen
On Tue, 2022-02-01 at 20:05 -0800, Jakub Kicinski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Tue, 1 Feb 2022 15:30:57 +0100 Steen Hegelund wrote:
> > Do not try to use any SKB fields after the packet has been passed up in the
> > receive stack.
> >
> > This error was reported as shown below:
>
> No need to spell it out, the tags speak for themselves.
>
> > Reported-by: kernel test robot <lkp@intel.com>
> > Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> >
>
> Drop this...
>
> > Fixes: f3cad2611a77 (net: sparx5: add hostmode with phylink support)
> >
>
> and this empty line - all the tags should be together.
>
> > Signed-off-by: Steen Hegelund <steen.hegelund@microchip.com>
> > ---
> > drivers/net/ethernet/microchip/sparx5/sparx5_packet.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/ethernet/microchip/sparx5/sparx5_packet.c
> > b/drivers/net/ethernet/microchip/sparx5/sparx5_packet.c
> > index dc7e5ea6ec15..ebdce4b35686 100644
> > --- a/drivers/net/ethernet/microchip/sparx5/sparx5_packet.c
> > +++ b/drivers/net/ethernet/microchip/sparx5/sparx5_packet.c
> > @@ -145,8 +145,8 @@ static void sparx5_xtr_grp(struct sparx5 *sparx5, u8 grp, bool byte_swap)
> > skb_put(skb, byte_cnt - ETH_FCS_LEN);
> > eth_skb_pad(skb);
> > skb->protocol = eth_type_trans(skb, netdev);
> > - netif_rx(skb);
> > netdev->stats.rx_bytes += skb->len;
> > + netif_rx(skb);
> > netdev->stats.rx_packets++;
>
> sorry to nit pick - wouldn't it be neater if both the stats were
> updated together? Looks a little strange that netif_rx() is in
> between the two now.
>
> > }
> >
> > --
> > 2.35.1
> >
>
prev parent reply other threads:[~2022-02-02 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 14:30 [PATCH net] net: sparx5: do not refer to skb after passing it on Steen Hegelund
2022-02-02 4:05 ` Jakub Kicinski
2022-02-02 8:23 ` Steen Hegelund [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=d55ed1f583c31df17e98300ca91996a2446f4523.camel@microchip.com \
--to=steen.hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).