mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: linux-kernel@vger.kernel.org, Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Eric Paris <eparis@redhat.com>, Don Dutile <ddutile@redhat.com>,
	chrisw@sous-sol.org
Subject: [PATCH 0/2] pci: refer to LSM when accessing device dependent config space
Date: Wed,  9 Feb 2011 22:11:50 -0800	[thread overview]
Message-ID: <1297318312-14309-1-git-send-email-chrisw@sous-sol.org> (raw)

Short patch series to make sure LSM gets visibility into attempt to
access device dependent config space.  Fixes a buglet I introduced in
de139a3 ("pci: check caps from sysfs file open to read device dependent
config space")

Chris Wright (2):
  security: add cred argument to security_capable()
  pci: use security_capable() when checking capablities during config
    space read

 drivers/pci/pci-sysfs.c  |    3 ++-
 include/linux/security.h |    6 +++---
 kernel/capability.c      |    2 +-
 security/security.c      |    5 ++---
 4 files changed, 8 insertions(+), 8 deletions(-)

-- 
1.7.3.4

             reply	other threads:[~2011-02-10  6:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10  6:11 Chris Wright [this message]
2011-02-10  6:11 ` [PATCH 1/2] security: add cred argument to security_capable() Chris Wright
2011-02-10 13:43   ` Serge E. Hallyn
2011-02-10 16:01   ` Casey Schaufler
2011-02-10 16:08     ` Chris Wright
2011-02-10 16:25       ` Casey Schaufler
2011-02-10  6:11 ` [PATCH 2/2] pci: use security_capable() when checking capablities during config space read Chris Wright
2011-02-10  8:23   ` James Morris
2011-02-10 23:58     ` [PATCH 2/2 v2] " Chris Wright
2011-02-14 17:14       ` Eric Paris
2011-03-04 18:25       ` Jesse Barnes
2011-02-11  7:01 ` [PATCH 0/2] pci: refer to LSM when accessing device dependent config space James Morris

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=1297318312-14309-1-git-send-email-chrisw@sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=ddutile@redhat.com \
    --cc=eparis@redhat.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®