[dpdk-dev] [PATCHv4 2/9] null: fix segfault when null_pmd added to bonding

Tetsuya Mukawa mukawa at igel.co.jp
Tue Sep 29 04:24:26 CEST 2015


On 2015/07/16 2:26, Tomasz Kulasek wrote:
> When device is added to the bonding, the link status callback is added to
> the slave's eth_dev->link_intr_cbs list. This list is not initialized for
> null pmd and adding it to the bonding segfaults application.
>
> This patch allocates and sets up required structures.
>
> Signed-off-by: Tomasz Kulasek <tomaszx.kulasek at intel.com>
> ---
>  drivers/net/null/rte_eth_null.c |   11 +++++++++++
>  1 file changed, 11 insertions(+)
>
> diff --git a/drivers/net/null/rte_eth_null.c b/drivers/net/null/rte_eth_null.c
> index e244595..a8b3191 100644
> --- a/drivers/net/null/rte_eth_null.c
> +++ b/drivers/net/null/rte_eth_null.c
> @@ -386,6 +386,7 @@ eth_dev_null_create(const char *name,
>  	const unsigned nb_rx_queues = 1;
>  	const unsigned nb_tx_queues = 1;
>  	struct rte_eth_dev_data *data = NULL;
> +	struct eth_driver *eth_drv = NULL;

Hi Tomasz,

Thanks for extending null pmd features.
Is it possible to use rte_null_pmd here?
Could you please check ring pmd? It may also uses rte_ring_pmd for link
status callback.

Tetsuya



More information about the dev mailing list