From: Anton Ivanov <anton.ivanov@cambridgegreys.com>
To: linux-um <linux-um@lists.infradead.org>
Subject: 64 bit time regression in recvmmsg()
Date: Fri, 29 Nov 2019 14:34:01 +0000 [thread overview]
Message-ID: <3820d68b-1d97-8f41-d55d-237d1695458c@cambridgegreys.com> (raw)
Hi all,
Unfortunately, it looks like the recent year 2038 have broken
compatibility for one particular syscall interface we use - recvmmsg.
The host now occasionally returns -22 (EINVAL) and the only way I see
for this to happen looking at the source is if when it gets something
bogus as a timeout.
I think I have eliminated all other possible sources for this error.
The picture can be observed when using a 64 bit host 5.2 kernel on a
Debian 64 bit buster userspace (glibc compiled vs 4.19 headers).
The code as it is written at present retries and by sheer luck and
perseverance it manages to work, but this needs to be fixed.
Brgds,
--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next reply other threads:[~2019-11-29 14:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 14:34 Anton Ivanov [this message]
2019-11-29 15:05 ` 64 bit time regression in recvmmsg() Geert Uytterhoeven
2019-11-29 15:17 ` Arnd Bergmann
2019-11-29 16:34 ` Anton Ivanov
2019-12-04 21:08 ` Arnd Bergmann
2019-12-05 9:41 ` Anton Ivanov
2019-12-06 17:49 ` Anton Ivanov
2019-12-06 20:06 ` Arnd Bergmann
2019-12-09 9:19 ` Invalid GSO - from 4.x (TBA) to 5.5-rc1. Was: " Anton Ivanov
2019-12-09 9:19 ` Anton Ivanov
2019-12-09 10:05 ` Anton Ivanov
2019-12-09 10:05 ` Anton Ivanov
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=3820d68b-1d97-8f41-d55d-237d1695458c@cambridgegreys.com \
--to=anton.ivanov@cambridgegreys.com \
--cc=linux-um@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.