From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH] igb_uio: fix refcount if open returns error
Date: Thu, 11 Oct 2018 13:48:48 +0200 [thread overview]
Message-ID: <2280183.FyIV3bEMkT@xps> (raw)
In-Reply-To: <2919e34a-f943-80fc-d2f0-d1c53fde0cae@intel.com>
26/09/2018 19:20, Ferruh Yigit:
> On 9/14/2018 4:30 PM, Stephen Hemminger wrote:
> > This fixes the problem of reference count leak if
> > igbuio_pci_enable_interrupts fails.
> >
> > Also, replace mutex and integer with a kernel atomic counter.
> > This is standard pattern for kernel devices.
> >
> > Fixes: 19685d5aa79c ("igb_uio: allow multi-process access")
> > Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied, thanks
prev parent reply other threads:[~2018-10-11 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 15:30 Stephen Hemminger
2018-09-26 17:20 ` Ferruh Yigit
2018-10-11 11:48 ` Thomas Monjalon [this message]
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=2280183.FyIV3bEMkT@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.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).