mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jike Song <jike.song@intel.com>
To: alex.williamson@redhat.com, serge@hallyn.com
Cc: kwankhede@nvidia.com, kraxel@redhat.com,
	linux-security-module@vger.kernel.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, Jike Song <jike.song@intel.com>
Subject: [v2 0/2] test capability for remote task
Date: Thu, 12 Jan 2017 16:52:01 +0800	[thread overview]
Message-ID: <1484211123-8139-1-git-send-email-jike.song@intel.com> (raw)

Sometimes vfio iommu type1 needs to pin memory for a remote task other
than current, thereby needs to test the CAP_IPC_LOCK capability for
that task.

The proper routine for this purpose is has_capability(), but it is
not yet exported for modules. None of currently exported capability-
testing symbols allows a specified task. So here in this series
has_capability() is exported then used in the vfio iommu type1 driver.



v2: -> Add Serge's Acked-by to PATCH [1/2]
    -> Remove the change in vfio_pin_pages_remote, since it's now guaranteed the 'current' process


Hi Alex,

I kept EXPORT_SYMBOL other than EXPORT_SYMBOL_GPL, since I'm still
worry about changing the type of existing exports in 'capability.c'.
I'm new to open-source fearing of violating GPL :)


Jike Song (2):
  capability: export has_capability
  vfio iommu type1: fix the testing of capability for remote task

 drivers/vfio/vfio_iommu_type1.c | 3 +--
 kernel/capability.c             | 1 +
 2 files changed, 2 insertions(+), 2 deletions(-)

-- 
1.9.3

             reply	other threads:[~2017-01-12  8:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12  8:52 Jike Song [this message]
2017-01-12  8:52 ` [v2 1/2] capability: export has_capability Jike Song
2017-01-12 22:22   ` James Morris
2017-01-12  8:52 ` [v2 2/2] vfio iommu type1: fix the testing of capability for remote task Jike Song
2017-01-12 22:22   ` James Morris
2017-01-13  6:52     ` Kirti Wankhede

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=1484211123-8139-1-git-send-email-jike.song@intel.com \
    --to=jike.song@intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=serge@hallyn.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

all inboxes | Powered by JetHome®