From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] drivers/net/pcap: fix segfault in pcap pmd
Date: Thu, 26 May 2016 13:32:48 +0000 [thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F010376D0@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <1464269389-24687-1-git-send-email-reshma.pattan@intel.com>
Self-Nacking.. wrong patch
> -----Original Message-----
> From: Pattan, Reshma
> Sent: Thursday, May 26, 2016 2:30 PM
> To: dev@dpdk.org
> Cc: Pattan, Reshma <reshma.pattan@intel.com>
> Subject: [PATCH] drivers/net/pcap: fix segfault in pcap pmd
>
> Testpmd application will crash in fclose() upon quit after running the below
> command.
>
> "sudo gdb --args ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf0 -n 4 --vdev
> 'eth_pcap0,tx_iface=enp1s0f1,rx_pcap=/tmp/test.pcap' -- --port-
> topology=chained -i"
>
> The reason is, pcap vdev creation with tx stream type as "iface" as in above
> command dont need member ''dumpers'' of "struct tx_pcaps", hence will not
> have memory allocated. But contains a garbage values, as local object of struct
> tx_pcaps is not initialized to 0 inside rte_pmd_pcap_dev_init(). So calling
> pcap_dump_close() on dumper as part of eth_dev_stop() is causing segfault in
> fclose().
>
> Fix is to initilize local object of struct tx_pcaps to 0.
> Also initiliaze local object of stcruct rx_pcaps to 0.
>
> So during eth_dev_stop(), pcap_dump_close() will not be called if dumper is
> NULL.
>
> Fixes:4c173302("pcap: add new driver")
>
> Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
> ---
> drivers/net/pcap/rte_eth_pcap.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/pcap/rte_eth_pcap.c b/drivers/net/pcap/rte_eth_pcap.c
> index c98e234..e0bb500 100644
> --- a/drivers/net/pcap/rte_eth_pcap.c
> +++ b/drivers/net/pcap/rte_eth_pcap.c
> @@ -978,8 +978,8 @@ rte_pmd_pcap_devinit(const char *name, const char
> *params)
> unsigned numa_node, using_dumpers = 0;
> int ret;
> struct rte_kvargs *kvlist;
> - struct rx_pcaps pcaps;
> - struct tx_pcaps dumpers;
> + struct rx_pcaps pcaps={0};
> + struct tx_pcaps dumpers={0};
>
> RTE_LOG(INFO, PMD, "Initializing pmd_pcap for %s\n", name);
>
> --
> 2.5.0
next prev parent reply other threads:[~2016-05-26 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 13:29 Reshma Pattan
2016-05-26 13:32 ` Pattan, Reshma [this message]
2016-05-26 13:35 Reshma Pattan
2016-05-26 17:57 ` Ferruh Yigit
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=3AEA2BF9852C6F48A459DA490692831F010376D0@IRSMSX109.ger.corp.intel.com \
--to=reshma.pattan@intel.com \
--cc=dev@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).