[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20100723000348.GD24905@sequoia.sous-sol.org>
Date: Thu, 22 Jul 2010 17:03:48 -0700
From: Chris Wright <chrisw@...s-sol.org>
To: Andrew Morton <akpm@...ux-foundataion.org>,
Al Viro <viro@...IV.linux.org.uk>,
"Serge E. Hallyn" <serge.hallyn@...onical.com>,
Christoph Hellwig <hch@...radead.org>
Cc: "Daniel P. Berrange" <berrange@...hat.com>,
linux-kernel@...r.kernel.org
Subject: [PATCH] blkdev: cgroup whitelist permission fix
The cgroup device whitelist code gets confused when trying to grant
permission to a disk partition that is not currently open. Part of
blkdev_open() includes __blkdev_get() on the whole disk. This simply
avoids the cgroup check for the whole disk case when opening a
partition. This bug describes the details.
https://bugzilla.redhat.com/show_bug.cgi?id=589662
Basically, the only ways to reliably allow a cgroup access to a partition
on a block device when using the whitelist are to 1) also give it access
to the whole block device or 2) make sure the partition is already open
in a different context.
Seems valid for 2.6.35 and -stable to me, as it's currently broken and
causes libvirt's container support to fail.
Acked-by: Serge E. Hallyn <serue@...ibm.com>
Tested-by: Serge E. Hallyn <serue@...ibm.com>
Cc: stable@...nel.org
Signed-off-by: Chris Wright <chrisw@...s-sol.org>
---
fs/block_dev.c | 10 ++++++----
1 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/fs/block_dev.c b/fs/block_dev.c
index 7346c96..09b107e 100644
--- a/fs/block_dev.c
+++ b/fs/block_dev.c
@@ -1315,10 +1315,12 @@ static int __blkdev_get(struct block_device *bdev, fmode_t mode, int for_part)
/*
* hooks: /n/, see "layering violations".
*/
- ret = devcgroup_inode_permission(bdev->bd_inode, perm);
- if (ret != 0) {
- bdput(bdev);
- return ret;
+ if (!for_part) {
+ ret = devcgroup_inode_permission(bdev->bd_inode, perm);
+ if (ret != 0) {
+ bdput(bdev);
+ return ret;
+ }
}
lock_kernel();
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists