From: Dan Carpenter <dan.carpenter@oracle.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [bug report] xsk: Propagate napi_id to XDP socket Rx path
Date: Tue, 8 Dec 2020 15:21:01 +0300 [thread overview]
Message-ID: <X89vkBAEFET+IchI@mwanda> (raw)
Hello Bj?rn T?pel,
This is a semi-automatic email about new static checker warnings.
The patch b02e5a0ebb17: "xsk: Propagate napi_id to XDP socket Rx
path" from Nov 30, 2020, leads to the following Smatch complaint:
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c:6580 ixgbe_setup_rx_resources()
error: we previously assumed 'rx_ring->q_vector' could be null (see line 6550)
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
6549
6550 if (rx_ring->q_vector)
^^^^^^^^^^^^^^^^^
Check for NULL
6551 ring_node = rx_ring->q_vector->numa_node;
6552
6553 rx_ring->rx_buffer_info = vmalloc_node(size, ring_node);
6554 if (!rx_ring->rx_buffer_info)
6555 rx_ring->rx_buffer_info = vmalloc(size);
6556 if (!rx_ring->rx_buffer_info)
6557 goto err;
6558
6559 /* Round up to nearest 4K */
6560 rx_ring->size = rx_ring->count * sizeof(union ixgbe_adv_rx_desc);
6561 rx_ring->size = ALIGN(rx_ring->size, 4096);
6562
6563 set_dev_node(dev, ring_node);
6564 rx_ring->desc = dma_alloc_coherent(dev,
6565 rx_ring->size,
6566 &rx_ring->dma,
6567 GFP_KERNEL);
6568 set_dev_node(dev, orig_node);
6569 if (!rx_ring->desc)
6570 rx_ring->desc = dma_alloc_coherent(dev, rx_ring->size,
6571 &rx_ring->dma, GFP_KERNEL);
6572 if (!rx_ring->desc)
6573 goto err;
6574
6575 rx_ring->next_to_clean = 0;
6576 rx_ring->next_to_use = 0;
6577
6578 /* XDP RX-queue info */
6579 if (xdp_rxq_info_reg(&rx_ring->xdp_rxq, adapter->netdev,
6580 rx_ring->queue_index, rx_ring->q_vector->napi.napi_id) < 0)
^^^^^^^^^^^^^^^^^^^
New unchecked dereference.
6581 goto err;
6582
regards,
dan carpenter
reply other threads:[~2020-12-08 12:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=X89vkBAEFET+IchI@mwanda \
--to=dan.carpenter@oracle.com \
--cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.