From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: linuxppc-dev@lists.ozlabs.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Daniel Axtens <dja@axtens.net>,
David Gibson <david@gibson.dropbear.id.au>,
Gavin Shan <gwshan@linux.vnet.ibm.com>
Subject: [PATCH kernel 0/2] powerpc/powernv: Fix crash on PF unbind when VF is passed
Date: Fri, 8 Apr 2016 16:36:42 +1000 [thread overview]
Message-ID: <1460097404-35422-1-git-send-email-aik@ozlabs.ru> (raw)
These 2 patches are to fix the crash which happens when the user (accidentally)
unbinds the driver of a physical function of a SRIOV device while
a virtual function is passed to a guest.
Please comment. Thanks!
There might be more work required in addition to this as it is not clear
what protects from races between pnv_ioda_free_pe and pnv_ioda_alloc_pe.
Gavin, please help.
Alexey Kardashevskiy (2):
powerpc/iommu: Get rid of default group_release()
powerpc/powernv/ioda2: Delay PE disposal
arch/powerpc/include/asm/iommu.h | 12 ++++++----
arch/powerpc/kernel/iommu.c | 14 ++++--------
arch/powerpc/platforms/powernv/pci-ioda.c | 38 ++++++++++++++++---------------
arch/powerpc/platforms/pseries/iommu.c | 17 +++++++-------
4 files changed, 40 insertions(+), 41 deletions(-)
--
2.5.0.rc3
next reply other threads:[~2016-04-08 6:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 6:36 Alexey Kardashevskiy [this message]
2016-04-08 6:36 ` [PATCH kernel 1/2] powerpc/iommu: Get rid of default group_release() Alexey Kardashevskiy
2016-04-08 7:14 ` kbuild test robot
2016-04-14 1:35 ` David Gibson
2016-04-21 0:02 ` Gavin Shan
2016-04-21 3:17 ` Alexey Kardashevskiy
2016-04-08 6:36 ` [PATCH kernel 2/2] powerpc/powernv/ioda2: Delay PE disposal Alexey Kardashevskiy
2016-04-14 1:40 ` David Gibson
2016-04-15 1:29 ` Alexey Kardashevskiy
2016-04-15 2:26 ` David Gibson
2016-04-21 0:21 ` Gavin Shan
2016-04-21 3:20 ` Alexey Kardashevskiy
2016-04-26 2:29 ` Alexey Kardashevskiy
2016-04-27 1:07 ` Gavin Shan
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=1460097404-35422-1-git-send-email-aik@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=dja@axtens.net \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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).