From: Aristeu Rozanski <aris@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
"Serge E. Hallyn" <serge@hallyn.com>
Subject: [PATCH] userns: improve uid/gid map collision detection
Date: Wed, 23 Jan 2013 11:02:21 -0500 [thread overview]
Message-ID: <20130123160221.GG17632@redhat.com> (raw)
Initial implementation of the uid/gid maps will enforce that the
maps should be in order and would prevent a use case like this from
being used:
0 1000 1
48 500 1
since the second entry both values should be bigger than the previous.
This patch implements a more elaborate collision detection allowing any
order to be used.
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Serge E. Hallyn" <serge@hallyn.com>
Signed-off-by: Aristeu Rozanski <aris@redhat.com>
diff --git a/kernel/user_namespace.c b/kernel/user_namespace.c
index 2b042c4..fb0e492 100644
--- a/kernel/user_namespace.c
+++ b/kernel/user_namespace.c
@@ -521,6 +521,28 @@ struct seq_operations proc_projid_seq_operations = {
static DEFINE_MUTEX(id_map_mutex);
+#define in_range(b,first,len) ((b)>=(first)&&(b)<(first)+(len))
+static inline int extent_collision(struct uid_gid_map *new_map,
+ struct uid_gid_extent *extent)
+{
+ int i;
+ struct uid_gid_extent *cur;
+
+ for (i = 0; i < new_map->nr_extents; i++) {
+ cur = &new_map->extent[i];
+ if (in_range(extent->first, cur->first, cur->count) ||
+ in_range(extent->first + extent->count, cur->first,
+ cur->count))
+ return 1;
+ if (in_range(extent->lower_first, cur->lower_first,
+ cur->count) ||
+ in_range(extent->lower_first + extent->count,
+ cur->lower_first, cur->count))
+ return 1;
+ }
+ return 0;
+}
+
static ssize_t map_write(struct file *file, const char __user *buf,
size_t count, loff_t *ppos,
int cap_setid,
@@ -634,10 +656,7 @@ static ssize_t map_write(struct file *file, const char __user *buf,
if ((extent->lower_first + extent->count) <= extent->lower_first)
goto out;
- /* For now only accept extents that are strictly in order */
- if (last &&
- (((last->first + last->count) > extent->first) ||
- ((last->lower_first + last->count) > extent->lower_first)))
+ if (extent_collision(&new_map, extent))
goto out;
new_map.nr_extents++;
next reply other threads:[~2013-01-23 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 16:02 Aristeu Rozanski [this message]
2013-01-24 4:44 ` [PATCH] userns: improve uid/gid map collision detection Serge E. Hallyn
2013-01-24 15:28 ` [PATCH v2] " Aristeu Rozanski
2013-01-25 0:46 ` Andrew Morton
2013-01-25 2:00 ` Eric W. Biederman
2013-01-25 14:03 ` Aristeu Rozanski
2013-01-26 2:31 ` Eric W. Biederman
2013-01-28 14:25 ` Aristeu Rozanski
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=20130123160221.GG17632@redhat.com \
--to=aris@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@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