From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: panzhe <panzhe@kylinos.cn>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3] gethostname02: Accept EOVERFLOW on alpha
Date: Tue, 09 Jun 2026 08:11:49 +0000 [thread overview]
Message-ID: <6a27cac6.62b8b855.1795d9.163e@mx.google.com> (raw)
In-Reply-To: <20260604072637.147497-1-panzhe@kylinos.cn>
Hi Panzhe,
> Hi Cyril,
>
> Thanks for your review.
>
> The ENAMETOOLONG note in man describes the mainstream glibc implementation based on uname(2), but alpha has its own arch-specific implementation calling raw gethostname syscall and returning EOVERFLOW.
> Alpha glibc source:
> https://codebrowser.dev/glibc/glibc/sysdeps/unix/sysv/linux/alpha/gethostname.c.html
>
> POSIX does not specify required errno here, this is existing upstream glibc behavior. I suggest accepting both errnos to resolve alpha test failures.
>
>
> Regards,
> panzhe
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
for context, it was useful to add the following patch to the discussion:
https://patchwork.ozlabs.org/project/glibc/patch/20260604092410.185621-1-panzhe@kylinos.cn/
For me it's ok, but we need to see this patch being merged to glibc, before
updating LTP upstream. Please ping us when this will be official.
Regards,
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-06-09 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <--compose>
2026-06-04 7:26 ` [LTP] [PATCH v3] gethostname02: Accept EOVERFLOW on alpha panzhe
2026-06-04 8:43 ` Cyril Hrubis
2026-06-09 8:11 ` Andrea Cervesato via ltp [this message]
2026-06-09 9:53 ` Cyril Hrubis
2026-06-03 1:49 panzhe
2026-06-03 9:31 ` Cyril Hrubis
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=6a27cac6.62b8b855.1795d9.163e@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=panzhe@kylinos.cn \
/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