From: Matthew Wilcox <willy@debian.org>
To: Luigi Gangitano <luigi@debian.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Issues with seteuid()?
Date: Mon, 13 Jan 2003 03:06:35 +0000 [thread overview]
Message-ID: <20030113030635.I26554@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1042386569.3329.4.camel@luigi>; from luigi@debian.org on Sun, Jan 12, 2003 at 04:49:29PM +0100
On Sun, Jan 12, 2003 at 04:49:29PM +0100, Luigi Gangitano wrote:
> I'm the Debian package maintainer for Squid (HTTP Proxy). I received the
> forwarded bug report describing issues in seteuid() on palinux. While
> using seteuid(), forked processes terminate with SEGV.
>
> Is it a known problem?
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?
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-01-13 3:06 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 [this message]
2003-01-13 3:11 ` Randolph Chung
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=20030113030635.I26554@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=luigi@debian.org \
--cc=parisc-linux@lists.parisc-linux.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