All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Anton Ivanov <anton.ivanov@cambridgegreys.com>,
	linux-um <linux-um@lists.infradead.org>
Subject: Re: 64 bit time regression in recvmmsg()
Date: Fri, 29 Nov 2019 16:17:45 +0100	[thread overview]
Message-ID: <CAK8P3a1mrFgRyh5Fgv-d8Szd2pq0T6Ac7wL3ogeYcf-Uyrg4ZQ@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdWuiGC4ay=f6M2H=-PLiffavnFSu8CPXE26euAi6aoY0w@mail.gmail.com>

On Fri, Nov 29, 2019 at 4:05 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Fri, Nov 29, 2019 at 3:34 PM Anton Ivanov
> <anton.ivanov@cambridgegreys.com> wrote:
> > 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.

I only see a single call to recvmmsg() in arch/um, in uml_vector_recvmmsg(),
and this passes a NULL timeout pointer, is this the one that broke or
should I be looking at something else?

Do I understand you right that the regression is on a pure 64-bit system?

     Arnd


  reply	other threads:[~2019-11-29 15:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29 14:34 64 bit time regression in recvmmsg() Anton Ivanov
2019-11-29 15:05 ` Geert Uytterhoeven
2019-11-29 15:17   ` Arnd Bergmann [this message]
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=CAK8P3a1mrFgRyh5Fgv-d8Szd2pq0T6Ac7wL3ogeYcf-Uyrg4ZQ@mail.gmail.com \
    --to=arnd@arndb.de \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=geert@linux-m68k.org \
    --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.