>>>>> Ivan Shmakov <i...@main.uusia.org> writes:
>>>>> Manuel Prinz <man...@debian.org> writes:

 >> thanks for the report! I also took this upstream, but unfortunately
 >> neither upstream nor I can reproduce the bug since we do not have
 >> multi-homed IPv6 hosts available for testing. If you could help us
 >> testing and/or provide us with further information this would be
 >> really great! I CC'ed Jeff (upstream) since I'm not exactly sure
 >> what he needs.

 > When working with the package recently, I've stumbled upon what may
 > be another manifestation of the same bug.  Now, I suspect that it's
 > not IPv6 addresses by itself that trigger the problem, but rather the
 > length of their respective string representations.

[…]

        Apparently, I was confused over the output like (as enabled by
        the ‘--mca btl_base_verbose 30 option’):

[n1-4.ncu.am-1.org:12674] btl: tcp: attempting to connect() to address 
192.168.57.85 on port 516

        Note that port 516 (be it TCP or UDP) is privileged and
        obviously cannot be used by a program run unprivileged.  Now, I
        see that it's not truncation, but a byte order problem — it's
        the port 1026 (#x402) that's meant here, not 516 (#x204.)  Which
        is most probably a consequence of a missing (or wrongly placed)
        ntohs () or htons () call.  Which, however, I assume to be a
        completely different issue.

-- 
FSF associate member #7257

Attachment: pgp5OMA2SgZQy.pgp
Description: PGP signature

Reply via email to