netdev - Re: [PATCH net-next 3/6] octeontx2-vf: Virtual function driver dupport

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200310144320.4f691cb6@kicinski-fedora-PC1C0HJN>
Date:   Tue, 10 Mar 2020 14:43:20 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     sunil.kovvuri@...il.com
Cc:     netdev@...r.kernel.org, davem@...emloft.net,
        Tomasz Duszynski <tduszynski@...vell.com>,
        Subbaraya Sundeep <sbhatta@...vell.com>,
        Geetha sowjanya <gakula@...vell.com>,
        Sunil Goutham <sgoutham@...vell.com>
Subject: Re: [PATCH net-next 3/6] octeontx2-vf: Virtual function driver
 dupport

On Wed, 11 Mar 2020 00:17:22 +0530 sunil.kovvuri@...il.com wrote:
> +#define DRV_NAME	"octeontx2-nicvf"
> +#define DRV_STRING	"Marvell OcteonTX2 NIC Virtual Function Driver"
> +#define DRV_VERSION	"1.0"

Please drop the driver version, kernel version should be used upstream.

> +
> +static const struct pci_device_id otx2_vf_id_table[] = {
> +	{ PCI_DEVICE(PCI_VENDOR_ID_CAVIUM, PCI_DEVID_OCTEONTX2_RVU_AFVF) },
> +	{ PCI_DEVICE(PCI_VENDOR_ID_CAVIUM, PCI_DEVID_OCTEONTX2_RVU_VF) },
> +	{ }
> +};
> +
> +MODULE_AUTHOR("Marvell International Ltd.");

Only people can be authors, please put your name here or remove this.

> +MODULE_DESCRIPTION(DRV_STRING);
> +MODULE_LICENSE("GPL v2");
> +MODULE_VERSION(DRV_VERSION);
> +MODULE_DEVICE_TABLE(pci, otx2_vf_id_table);

> +static netdev_tx_t otx2vf_xmit(struct sk_buff *skb, struct net_device *netdev)
> +{
> +	struct otx2_nic *vf = netdev_priv(netdev);
> +	int qidx = skb_get_queue_mapping(skb);
> +	struct otx2_snd_queue *sq;
> +	struct netdev_queue *txq;
> +
> +	/* Check for minimum and maximum packet length */
> +	if (skb->len <= ETH_HLEN ||
> +	    (!skb_shinfo(skb)->gso_size && skb->len > vf->max_frs)) {

These should never happen (if they do we need to fix the stack, not
sprinkle all the drivers with checks like this).

> +		dev_kfree_skb(skb);
> +		return NETDEV_TX_OK;
> +	}
> +
> +	sq = &vf->qset.sq[qidx];
> +	txq = netdev_get_tx_queue(netdev, qidx);
> +
> +	if (!otx2_sq_append_skb(netdev, sq, skb, qidx)) {
> +		netif_tx_stop_queue(txq);
> +
> +		/* Check again, incase SQBs got freed up */
> +		smp_mb();
> +		if (((sq->num_sqbs - *sq->aura_fc_addr) * sq->sqe_per_sqb)
> +							> sq->sqe_thresh)
> +			netif_tx_wake_queue(txq);
> +
> +		return NETDEV_TX_BUSY;
> +	}
> +
> +	return NETDEV_TX_OK;
> +}

> +static void otx2vf_reset_task(struct work_struct *work)
> +{
> +	struct otx2_nic *vf = container_of(work, struct otx2_nic, reset_task);
> +
> +	if (!netif_running(vf->netdev))
> +		return;
> +
> +	otx2vf_stop(vf->netdev);
> +	vf->reset_count++;
> +	otx2vf_open(vf->netdev);

What's the locking around here? Can user call open/stop while this is
running?

> +	netif_trans_update(vf->netdev);
> +}

> +static int otx2vf_realloc_msix_vectors(struct otx2_nic *vf)
> +{
> +	struct otx2_hw *hw = &vf->hw;
> +	int num_vec, err;
> +
> +	num_vec = hw->nix_msixoff;
> +	num_vec += NIX_LF_CINT_VEC_START + hw->max_queues;
> +
> +	otx2vf_disable_mbox_intr(vf);
> +	pci_free_irq_vectors(hw->pdev);
> +	pci_free_irq_vectors(hw->pdev);

Why free IRQs twice?

> +	err = otx2vf_register_mbox_intr(vf, false);
> +	if (err)
> +		return err;

return otx2vf_re..