From: Andrew Morton <akpm@linux-foundation.org>
To: Joe Malicki <jmalicki@metacarta.com>
Cc: linux-kernel@vger.kernel.org, jmalicki@metacarta.com,
bakerkj@metacarta.com, mitz@metacarta.com
Subject: Re: BUG: setuid sometimes doesn't.
Date: Wed, 25 Feb 2009 16:28:36 -0800 [thread overview]
Message-ID: <20090225162836.63fce3c4.akpm@linux-foundation.org> (raw)
In-Reply-To: <9683328.9717571235603514325.JavaMail.root@ouachita>
On Wed, 25 Feb 2009 18:11:54 -0500 (EST)
Joe Malicki <jmalicki@metacarta.com> wrote:
>
wow, good bug report!
>
> Very rarely, we experience a setuid program not properly getting
> the euid of its owner.
Do you know which euid it _does_ get? Is it unchanged, or is it random
garbage, or...?
next prev parent reply other threads:[~2009-02-26 0:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <10783026.9717361235603356623.JavaMail.root@ouachita>
2009-02-25 23:11 ` BUG: setuid sometimes doesn't Joe Malicki
2009-02-26 0:28 ` Andrew Morton [this message]
2009-02-26 13:17 ` Joe Malicki
2009-02-26 12:06 ` Joe Malicki
2009-02-26 16:06 ` Hugh Dickins
[not found] <15171620.10049841236049960269.JavaMail.root@ouachita>
2009-03-03 3:16 ` Joe Malicki
2009-03-03 11:16 ` Hugh Dickins
2009-03-04 1:28 ` Joe Malicki
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=20090225162836.63fce3c4.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bakerkj@metacarta.com \
--cc=jmalicki@metacarta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mitz@metacarta.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