* Linus Torvalds (torvalds@transmeta.com) wrote:
> On Wed, 9 Oct 2002, Chris Wright wrote:
> >
> > Daniel Jacobowitz noticed that sys_capget is not behaving properly when
> > called with pid of 0. It is supposed to return current capabilities,
> > not those of swapper. Also cleaned up some duplicate code from a merge
> > error. Patch is tested, please apply.
>
> This is not correct. You drop the tasklist_lock before you actually set
> read the capabilities, which means that by the time you read them, the
> task you looked up may not be there any more.
Doh...feeling dumb...
The patch below fixes my oversight. The locking is left the way it was,
and just the pid 0 part is fixed as well as the duplicate code removed.
This still applies against bk-curr and I tested it on 2.5.41.
thanks,
-chris
--- 2.5.41/kernel/capability.c Sun Sep 15 12:19:29 2002
+++ 2.4.41-capget/kernel/capability.c Thu Oct 10 14:36:29 2002
@@ -33,7 +33,7 @@
int ret = 0;
pid_t pid;
__u32 version;
- task_t *target;
+ task_t *target = current;
struct __user_cap_data_struct data;
if (get_user(version, &header->version))
@@ -54,15 +54,14 @@
spin_lock(&task_capability_lock);
read_lock(&tasklist_lock);
- target = find_task_by_pid(pid);
- if (!target) {
- ret = -ESRCH;
- goto out;
+ if (pid && pid != current->pid) {
+ target = find_task_by_pid(pid);
+ if (!target) {
+ ret = -ESRCH;
+ goto out;
+ }
}
- data.permitted = cap_t(target->cap_permitted);
- data.inheritable = cap_t(target->cap_inheritable);
- data.effective = cap_t(target->cap_effective);
ret = security_ops->capget(target, &data.effective, &data.inheritable, &data.permitted);
out:
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Oct 15 2002 - 22:00:39 EST