From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
Subject: [Bug 42704] execve may return EAGAIN on v3.1 or later
Date: Tue, 17 Apr 2012 19:03:47 GMT
Message-ID: <201204171903.q3HJ3l34011784@bugzilla.kernel.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Return-path:
In-Reply-To:
Sender: linux-man-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
List-Id: linux-man@vger.kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=42704
Michael Kerrisk changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
--- Comment #1 from Michael Kerrisk 2012-04-17 19:03:47 ---
Vasiliy,
Thanks for raising this bug. I think the best approach would be to leave the
existing EAGAIN text in the set*uid pages (possibly with a note about v3.1
changes), and add some text to the execve.2 page.
However, I have a question: I can understand adding the check to execve(), but
why was it removed from set*uid()? Surely it was still useful to applications
that actually do check the return status from set*uid()?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html