[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <998248d1-aa5f-45e0-813e-d0565fc952d3@intel.com>
Date: Wed, 14 Feb 2024 13:56:17 -0800
From: Jacob Keller <jacob.e.keller@...el.com>
To: Rand Deeb <rand.sec96@...il.com>, "David S . Miller"
<davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>,
<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>
CC: <deeb.rand@...fident.ru>, <lvc-project@...uxtesting.org>,
<voskresenski.stanislav@...fident.ru>
Subject: Re: [PATCH] dl2k: Fix potential NULL pointer dereference in
receive_packet()
On 2/13/2024 12:09 PM, Rand Deeb wrote:
The subject doesn't indicate which tree for netdev it would target, but
this seems like an obvious bug fix for net.
> @@ -972,6 +972,14 @@ receive_packet (struct net_device *dev)
> np->rx_buf_sz,
> DMA_FROM_DEVICE);
> }
> + if (skb == NULL) {
> + np->rx_ring[entry].fraginfo = 0;
> + printk (KERN_INFO
> + "%s: receive_packet: "
> + "Unable to re-allocate Rx skbuff.#%d\n",
> + dev->name, entry);
You could use netdev_warn here instead of printk, which would include
the device information. I checked a couple other drivers and none of
them appear to log any message when this fails. A handful increment a
driver count of how many allocation failures occurred. I'm not sure how
helpful this print would be in practice.
With or without changes to the printed warning message:
Reviewed-by: Jacob Keller <jacob.e.keller@...el.com>
Powered by blists - more mailing lists