Hello!
On Sun, Sep 19, 2010 at 01:54:23PM +0200, Manuel Menal wrote:
> As a sidenote, this also makes us able to use sshd with
> UsePrivilegeSeparation set to yes (which used to fail because it sends
> the tty fd through sendmsg() with SCM_RIGHTS, which fails silently
> without your patch).
Confi
Good catch. As Roland notes the old code here has the restart race
bug. Also it was probably a leak because I think nothing here wa
counting he new make send instance the way we normally wrap all uses
of make send.
On Sunday, September 19, 2010, Manuel Menal wrote:
> On 27/07/2010 17:39, Emilio P
Manuel Menal, le Sun 19 Sep 2010 13:54:23 +0200, a écrit :
> Here is a very simple fix for this bug:
Applied.
Samuel
On 27/07/2010 17:39, Emilio Pozuelo Monfort wrote:
> Hi,
Hello,
> While adding support for SCM_RIGHTS to glibc, I've created a testcase that
> sends
> and receives some ports on the result of a socketpair() call. The ports sent
> were initially the two ports result of another socketpair() call,
> On 28/07/10 00:53, Roland McGrath wrote:
> > I don't know off hand why you're getting that failure mode. But in general
> > you can't use MACH_MSG_TYPE_MOVE_SEND in Hurd RPC arguments (only for
> > replies) because of the interrupt retry issue. That could be related
> > to this failure though I
On 28/07/10 00:53, Roland McGrath wrote:
> I don't know off hand why you're getting that failure mode. But in general
> you can't use MACH_MSG_TYPE_MOVE_SEND in Hurd RPC arguments (only for
> replies) because of the interrupt retry issue. That could be related
> to this failure though I can't rea
I don't know off hand why you're getting that failure mode. But in general
you can't use MACH_MSG_TYPE_MOVE_SEND in Hurd RPC arguments (only for
replies) because of the interrupt retry issue. That could be related
to this failure though I can't really see how at the moment.
Thanks,
Roland
Hi,
While adding support for SCM_RIGHTS to glibc, I've created a testcase that sends
and receives some ports on the result of a socketpair() call. The ports sent
were initially the two ports result of another socketpair() call, and it was
working fine, but then I tried with the result of a couple
