Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <tausq@debian.org>
To: Matthew Wilcox <willy@debian.org>
Cc: Luigi Gangitano <luigi@debian.org>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Issues with seteuid()?
Date: Sun, 12 Jan 2003 19:11:09 -0800	[thread overview]
Message-ID: <20030113031109.GI1177@tausq.org> (raw)
In-Reply-To: <20030113030635.I26554@parcelfarce.linux.theplanet.co.uk>

> I wonder how it can be a problem at all.  The kernel implements only
> sys_setresuid() and i would imagine that glibc implements both
> seteuid() and setresuid() in terms of this system call.
> 
> Perhaps someone who's willing to touch glibc would care to comment?

seteuid() works fine in simple tests. i don't think it's seteuid...
something else is broken. can someone provide a simple test case for the
segfault?

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

  reply	other threads:[~2003-01-13  3:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-12 15:49 [parisc-linux] Issues with seteuid()? Luigi Gangitano
2003-01-13  3:06 ` Matthew Wilcox
2003-01-13  3:11   ` Randolph Chung [this message]
2003-01-29 17:01     ` Joel Soete
2003-01-30  7:03       ` Randolph Chung
2003-01-30  7:37         ` Joel Soete
2003-01-29 13:58 ` Joel Soete
  -- strict thread matches above, loose matches on Subject: below --
2003-01-13 10:19 jsoe0708
     [not found] <20030130073214.GJ20940@tausq.org>
     [not found] ` <3E35C33F0000094B@ocpmta3.freegates.net>
2003-01-30  7:54   ` Randolph Chung
2003-01-30  8:28     ` Joel Soete
2003-01-30 13:03       ` Joel Soete

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=20030113031109.GI1177@tausq.org \
    --to=tausq@debian.org \
    --cc=luigi@debian.org \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=willy@debian.org \
    /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