* [Intel-wired-lan] [bug report] iavf: allow null RX descriptors
@ 2019-06-20 7:45 Dan Carpenter
2019-06-24 12:19 ` Dan Carpenter
0 siblings, 1 reply; 2+ messages in thread
From: Dan Carpenter @ 2019-06-20 7:45 UTC (permalink / raw)
To: intel-wired-lan
Hello Mitch Williams,
This is a semi-automatic email about new static checker warnings.
The patch efa14c398582: "iavf: allow null RX descriptors" from May
14, 2019, leads to the following Smatch complaint:
drivers/net/ethernet/intel/iavf/iavf_txrx.c:1533 iavf_clean_rx_irq()
warn: variable dereferenced before check 'rx_buffer' (see line 1526)
drivers/net/ethernet/intel/iavf/iavf_txrx.c
1515
1516 size = (qword & IAVF_RXD_QW1_LENGTH_PBUF_MASK) >>
1517 IAVF_RXD_QW1_LENGTH_PBUF_SHIFT;
1518
1519 iavf_trace(clean_rx_irq, rx_ring, rx_desc, skb);
1520 rx_buffer = iavf_get_rx_buffer(rx_ring, size);
1521
1522 /* retrieve a buffer from the ring */
1523 if (skb)
skb is non-NULL so ignore this path.
1524 iavf_add_rx_frag(rx_ring, rx_buffer, skb, size);
1525 else if (ring_uses_build_skb(rx_ring))
1526 skb = iavf_build_skb(rx_ring, rx_buffer, size);
^^^^^^^^^
1527 else
1528 skb = iavf_construct_skb(rx_ring, rx_buffer, size);
^^^^^^^^^
These functions both dereference "rx_buffer" and might set skb to NULL.
1529
1530 /* exit if we failed to retrieve a buffer */
1531 if (!skb) {
1532 rx_ring->rx_stats.alloc_buff_failed++;
1533 if (rx_buffer)
^^^^^^^^^^^^^
If "rx_buffer" is NULL then we would already have crashed.
1534 rx_buffer->pagecnt_bias++;
1535 break;
regards,
dan carpenter
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Intel-wired-lan] [bug report] iavf: allow null RX descriptors
2019-06-20 7:45 [Intel-wired-lan] [bug report] iavf: allow null RX descriptors Dan Carpenter
@ 2019-06-24 12:19 ` Dan Carpenter
0 siblings, 0 replies; 2+ messages in thread
From: Dan Carpenter @ 2019-06-24 12:19 UTC (permalink / raw)
To: intel-wired-lan
On Thu, Jun 20, 2019 at 10:45:16AM +0300, Dan Carpenter wrote:
> Hello Mitch Williams,
>
> This is a semi-automatic email about new static checker warnings.
>
> The patch efa14c398582: "iavf: allow null RX descriptors" from May
> 14, 2019, leads to the following Smatch complaint:
>
> drivers/net/ethernet/intel/iavf/iavf_txrx.c:1533 iavf_clean_rx_irq()
> warn: variable dereferenced before check 'rx_buffer' (see line 1526)
>
> drivers/net/ethernet/intel/iavf/iavf_txrx.c
> 1515
> 1516 size = (qword & IAVF_RXD_QW1_LENGTH_PBUF_MASK) >>
> 1517 IAVF_RXD_QW1_LENGTH_PBUF_SHIFT;
> 1518
> 1519 iavf_trace(clean_rx_irq, rx_ring, rx_desc, skb);
> 1520 rx_buffer = iavf_get_rx_buffer(rx_ring, size);
> 1521
> 1522 /* retrieve a buffer from the ring */
> 1523 if (skb)
>
> skb is non-NULL so ignore this path.
>
> 1524 iavf_add_rx_frag(rx_ring, rx_buffer, skb, size);
> 1525 else if (ring_uses_build_skb(rx_ring))
> 1526 skb = iavf_build_skb(rx_ring, rx_buffer, size);
> ^^^^^^^^^
> 1527 else
> 1528 skb = iavf_construct_skb(rx_ring, rx_buffer, size);
> ^^^^^^^^^
> These functions both dereference "rx_buffer" and might set skb to NULL.
Oh... Huh. They aren't *supposed* to dereference rx_buffer, but the
NULL checks are too late.
regards,
dan carpenter
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-06-24 12:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-06-20 7:45 [Intel-wired-lan] [bug report] iavf: allow null RX descriptors Dan Carpenter
2019-06-24 12:19 ` Dan Carpenter
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox