From: Daniel Jacobowitz <dan@debian.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Chris Wright <chris@wirex.com>, linux-kernel@vger.kernel.org
Subject: [PATCH] sys_capget should use current if the pid argument is 0
Date: Tue, 19 Nov 2002 16:14:53 -0500 [thread overview]
Message-ID: <20021119211453.GA20562@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0210111954280.5671-100000@home.transmeta.com>
On Fri, Oct 11, 2002 at 07:58:46PM -0700, Linus Torvalds wrote:
>
> On Thu, 10 Oct 2002, Chris Wright wrote:
> >
> > 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.
>
> All right, call me stupid, but twhere is the "duplication" in the code you
> removed?
>
> I see the "security/capability.c" thing, yes, but I also look at
> "security/dummy.c", and it appears that at least for that case nobody
> would ever initialize the capabilities that we return to user space at
> all.
>
> So there's a bug somewhere there, and removing the duplication makes
> things worse (admittedly for a case which isn't enabled in the regular
> kernel, but still..)
>
> So I'd ask you to have patience with me, and send a third patch that gets
> this thing right too..
Since this is still broken a month later... I don't know what to do
about the "duplication" question, but I'll leave that to Chris. This
is the uncontroversial portion of Chris's patch; its affect is to
change my zsh shell prompt back to a '%' as I'd expect.
Linus, please apply.
[PATCH] sys_capget should use current if the pid argument is 0
===== kernel/capability.c 1.6 vs edited =====
--- 1.6/kernel/capability.c Sat Sep 14 09:18:49 2002
+++ edited/kernel/capability.c Tue Nov 19 16:10:59 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,10 +54,12 @@
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);
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-11-19 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 0:15 [PATCH] 2.5.41 capget fix Chris Wright
2002-10-10 19:36 ` Linus Torvalds
2002-10-10 21:47 ` Chris Wright
2002-10-12 2:58 ` Linus Torvalds
2002-11-19 21:14 ` Daniel Jacobowitz [this message]
2002-11-20 0:55 ` [PATCH] sys_capget should use current if the pid argument is 0 Chris Wright
2002-11-20 2:49 ` [PATCH] remove duplicated assignment from sys_capget Chris Wright
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=20021119211453.GA20562@nevyn.them.org \
--to=dan@debian.org \
--cc=chris@wirex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.