From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13671] openSSH server closes connection before authentication is finished
Date: Wed, 24 Mar 2021 11:35:40 +0000 [thread overview]
Message-ID: <bug-13671-163-vdKhb6KtRg@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13671-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13671
--- Comment #7 from Geert Lens <g.lens@livetech-systems.com> ---
When I use the Arm ARM 2020.11 toolchain (GCC 10.2, GDB 10.1, glibc 2.31,
Binutils 2.35.1) to build 2021.02, the OpenSSH is being killed when trying to
login.
I made a strace using that setup and got this:
[pid 14957] write(2, "debug3: mm_request_send entering"..., 52 <unfinished ...>
[pid 15027] write(7, "\0\0\0/\0\0\0\6\0\0\0'input_userauth_reque"..., 51
<unfinished ...>
[pid 14957] <... write resumed>) = 52
[pid 15027] <... write resumed>) = 51
[pid 14957] poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}], 2, -1
<unfinished ...>
[pid 15027] write(7, "\0\0\08\0\0\0\7\0\0\0000user_specific_delay:"..., 60
<unfinished ...>
[pid 14957] <... poll resumed>) = 2 ([{fd=5, revents=POLLIN}, {fd=6,
revents=POLLIN}])
[pid 15027] <... write resumed>) = 60
[pid 14957] read(6, <unfinished ...>
[pid 15027] clock_gettime(CLOCK_BOOTTIME, <unfinished ...>
[pid 14957] <... read resumed>"\0\0\0/", 4) = 4
[pid 15027] <... clock_gettime resumed>{tv_sec=3303, tv_nsec=218403125}) = 0
[pid 14957] read(6, <unfinished ...>
[pid 15027] write(7, "\0\0\0[\0\0\0\7\0\0\0Sensure_minimum_time_"..., 95
<unfinished ...>
[pid 14957] <... read resumed>"\0\0\0\6\0\0\0'input_userauth_request: "..., 47)
= 47
[pid 15027] <... write resumed>) = 95
[pid 14957] write(2, "debug2: input_userauth_request: "..., 59 <unfinished ...>
[pid 15027] clock_nanosleep_time64(CLOCK_REALTIME, 0, {tv_sec=0,
tv_nsec=24392751410935043}, <unfinished ...>
[pid 14957] <... write resumed>) = 59
[pid 15027] <... clock_nanosleep_time64 resumed> <unfinished ...>) = ?
[pid 14957] poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}], 2, -1
<unfinished ...>
[pid 15027] +++ killed by SIGSYS +++
<... poll resumed>) = 2 ([{fd=5, revents=POLLIN}, {fd=6,
revents=POLLIN}])
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=15027, si_uid=1001,
si_status=SIGSYS, si_utime=8, si_stime=4} ---
It looks similar to what you could reproduce, the only difference is that the
call to clock_nanosleep_time64() is aborted with SIGSYS.
When I use the Arm ARM 2019.2 toolchain (GCC 9.2.1, GDB 8.3.0, glibc 2.30,
Binutils 2.33.1) to build 2021.02, OpenSSH is not being killed and I am able to
login in.
Do you have any idea what could cause this?
Furthermore, I am using the Linux kernel v4.14.78 in my project.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-24 11:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 19:28 [Buildroot] [Bug 13671] New: openSSH server closes connection before authentication is finished bugzilla at busybox.net
2021-03-23 19:30 ` [Buildroot] [Bug 13671] " bugzilla at busybox.net
2021-03-23 20:01 ` bugzilla at busybox.net
2021-03-23 20:45 ` bugzilla at busybox.net
2021-03-23 21:16 ` bugzilla at busybox.net
2021-03-23 22:10 ` bugzilla at busybox.net
2021-03-23 22:32 ` bugzilla at busybox.net
2021-03-24 11:35 ` bugzilla at busybox.net [this message]
2021-03-25 21:09 ` bugzilla at busybox.net
2021-03-27 16:51 ` bugzilla at busybox.net
2021-03-28 17:41 ` bugzilla at busybox.net
2021-03-30 10:18 ` bugzilla at busybox.net
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=bug-13671-163-vdKhb6KtRg@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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