From: Felix von Leitner <felix-kernel@fefe.de>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-test3: setuid32(8) returns EAGAIN (WTF?!)
Date: Sun, 17 Aug 2003 03:03:36 +0200 [thread overview]
Message-ID: <20030817010336.GA12079@codeblau.de> (raw)
I just changed from 2.5.75 to 2.6.0-test3 and suddenly my imap server
fails to start (it's dovecot). It wrote to syslog:
Aug 17 02:58:02 hellhound dovecot: Dovecot starting up
Aug 17 02:58:03 hellhound imap-login: setuid(8) failed: Resource temporarily unavailable
Aug 17 02:58:03 hellhound dovecot: Login process died too early - shutting down
So I strace -f it, and sure enough, here is what happens:
[init, fork, tzfile...]
8094 chroot("/var/run/dovecot//login") = 0
8094 chdir("/") = 0
8094 setuid32(0x8) = -1 EAGAIN (Resource temporarily unavailable)
Now this does not appear to be a valid return value for setuid32, and
my understanding of POSIX and Susv3 is that dovecot is absolutely right
in barfing at this.
Why is this happening? Please fix!
Felix
PS: Time for a brown paper bag bug-fix release, if you ask me.
next reply other threads:[~2003-08-17 1:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-17 1:03 Felix von Leitner [this message]
2003-08-18 19:43 ` 2.6.0-test3: setuid32(8) returns EAGAIN (WTF?!) Andries Brouwer
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=20030817010336.GA12079@codeblau.de \
--to=felix-kernel@fefe.de \
--cc=linux-kernel@vger.kernel.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 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.