From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: Chaoyong He <chaoyong.he@corigine.com>,
Stephen Hemminger <stephen@networkplumber.org>,
stable@dpdk.org, Chenbo Xia <chenbox@nvidia.com>,
Nipun Gupta <nipun.gupta@amd.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Long Wu <long.wu@corigine.com>, Zerun Fu <zerun.fu@corigine.com>,
Konrad Sztyber <konrad.sztyber@intel.com>
Subject: Re: [PATCH v3] bus/pci: don't open uio device in secondary process
Date: Thu, 24 Oct 2024 11:05:53 +0200 [thread overview]
Message-ID: <CAJFAV8xA+znr6RfzpZCD0Sq=JXnbugZ6N4AtP_D_awWme_dT1w@mail.gmail.com> (raw)
In-Reply-To: <20241011111533.20746-1-konrad.sztyber@intel.com>
On Fri, Oct 11, 2024 at 1:17 PM Konrad Sztyber <konrad.sztyber@intel.com> wrote:
>
> The uio_pci_generic driver clears the bus master bit when the device
> file is closed. So, when the secondary process terminates after probing
> a device, that device becomes unusable in the primary process.
>
> To avoid that, the device file is now opened only in the primary process
> and the secondary gets it over UNIX domain socket via SCM_RIGHTS.
>
> Fixes: 847d78fb9530 ("bus/pci: fix FD in secondary process")
> Cc: stable@dpdk.org
>
> Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com>
Recheck-request: rebase=main,iol-compile-amd64-testing
--
David Marchand
next prev parent reply other threads:[~2024-10-24 9:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 10:40 [PATCH] " Konrad Sztyber
2024-08-29 5:53 ` Chaoyong He
2024-08-29 8:06 ` Chenbo Xia
2024-08-29 8:57 ` [PATCH v2] " Konrad Sztyber
2024-08-30 3:48 ` Chenbo Xia
2024-10-11 11:15 ` [PATCH v3] " Konrad Sztyber
2024-10-24 9:05 ` David Marchand [this message]
2024-10-07 17:49 ` [PATCH] " Stephen Hemminger
2024-10-09 10:11 ` Konrad Sztyber
2024-10-09 15:12 ` Stephen Hemminger
2024-10-11 6:38 ` Konrad Sztyber
2024-10-11 6:46 ` David Marchand
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='CAJFAV8xA+znr6RfzpZCD0Sq=JXnbugZ6N4AtP_D_awWme_dT1w@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=chaoyong.he@corigine.com \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=konrad.sztyber@intel.com \
--cc=long.wu@corigine.com \
--cc=nipun.gupta@amd.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=zerun.fu@corigine.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).