From: Chris Wright Date: Tue, 15 Feb 2011 01:21:49 +0000 (-0800) Subject: pci: use security_capable() when checking capablities during config space read X-Git-Tag: v2.6.37.2~41 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ba5e8f48f799e61d865adb2830bb78fce3267762;p=pandora-kernel.git pci: use security_capable() when checking capablities during config space read commit a628e7b87e100befac9702aa0c3b9848a7685e49 upstream. This reintroduces commit 47970b1b which was subsequently reverted as f00eaeea. The original change was broken and caused X startup failures and generally made privileged processes incapable of reading device dependent config space. The normal capable() interface returns true on success, but the LSM interface returns 0 on success. This thinko is now fixed in this patch, and has been confirmed to work properly. So, once again...Eric Paris noted that commit de139a3 ("pci: check caps from sysfs file open to read device dependent config space") caused the capability check to bypass security modules and potentially auditing. Rectify this by calling security_capable() when checking the open file's capabilities for config space reads. Reported-by: Eric Paris Tested-by: Dave Young Acked-by: James Morris Cc: Dave Airlie Cc: Alex Riesen Cc: Sedat Dilek Cc: Linus Torvalds Signed-off-by: Chris Wright Signed-off-by: James Morris Signed-off-by: Greg Kroah-Hartman --- Reading git-diff-tree failed