DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 1/1] net/mlx5: fix sharing context destroy	order
Date: Mon, 8 Apr 2019 06:00:15 +0000	[thread overview]
Message-ID: <AM0PR0502MB3795B5C528F6F99C93F1AC08C32C0@AM0PR0502MB3795.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1554470945-14357-1-git-send-email-viacheslavo@mellanox.com>

Friday, April 5, 2019 4:29 PM, Viacheslav Ovsiienko:
> Subject: [dpdk-dev] [PATCH v2 1/1] net/mlx5: fix sharing context destroy
> order
> 
> At the mlx5 device closing the shared IB context was destroyed before
> cleanup routines completion. As it was found on some setups (Netlink fails
> with old kernel drivers and we have to use sysfs to retrieve interface index,
> this requires IB device name, which is stored in shared context) the
> mlx5_nl_mac_addr_flush() requires IB device name, and if shared context is
> removed it causes the segmentation fault.
> 
> Fixes: 17e19bc4dde7 ("net/mlx5: add IB shared context alloc/free functions")
> 
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>

Applied to next-net-mlx, thanks. 

  parent reply	other threads:[~2019-04-08  6:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03 14:14 [dpdk-dev] [PATCH " Viacheslav Ovsiienko
2019-04-03 14:14 ` Viacheslav Ovsiienko
2019-04-05 13:29 ` [dpdk-dev] [PATCH v2 " Viacheslav Ovsiienko
2019-04-05 13:29   ` Viacheslav Ovsiienko
2019-04-08  6:00   ` Shahaf Shuler [this message]
2019-04-08  6:00     ` Shahaf Shuler

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=AM0PR0502MB3795B5C528F6F99C93F1AC08C32C0@AM0PR0502MB3795.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=viacheslavo@mellanox.com \
    /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).