From: Cyril Hrubis <chrubis@suse.cz>
To: panzhe <panzhe@kylinos.cn>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3] gethostname02: Accept EOVERFLOW on alpha
Date: Thu, 4 Jun 2026 10:43:51 +0200 [thread overview]
Message-ID: <aiE6x3L3trEaeQKk@yuki.lan> (raw)
In-Reply-To: <20260604072637.147497-1-panzhe@kylinos.cn>
Hi!
> 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
This really looks like a inconsistency in glibc. I suggest to ask a
question if this should be fixed in glibc on libc-alpha mailing list
first. Please CC ltp mailing list when you ask this question.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-06-04 8:44 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 [this message]
2026-06-09 8:11 ` Andrea Cervesato via ltp
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=aiE6x3L3trEaeQKk@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--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