From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Leonardo Bras Soares Passos <leobras@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Juan Quintela <quintela@redhat.com>, Peter Xu <peterx@redhat.com>
Subject: Re: [PULL 00/16] migration queue
Date: Mon, 16 May 2022 16:30:07 +0100 [thread overview]
Message-ID: <YoJt/6S0t3xFS6b/@stefanha-x1.localdomain> (raw)
In-Reply-To: <YoIi01eSEK38R03/@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1668 bytes --]
On Mon, May 16, 2022 at 11:09:23AM +0100, Daniel P. Berrangé wrote:
> On Mon, May 16, 2022 at 10:40:15AM +0100, Daniel P. Berrangé wrote:
> > On Mon, May 16, 2022 at 09:51:12AM +0100, Stefan Hajnoczi wrote:
> > > On Wed, May 11, 2022 at 12:40:07AM -0300, Leonardo Bras Soares Passos wrote:
> > > > From a previous thread:
> > > >
> > > > On Thu, Apr 28, 2022 at 1:20 PM Dr. David Alan Gilbert
> > > > <dgilbert@redhat.com> wrote:
> > > > >
> > > > > Leo:
> > > > > Unfortunately this is failing a couple of CI tests; the MSG_ZEROCOPY
> > > > > one I guess is the simpler one; I think Stefanha managed to find the
> > > > > liburing fix for the __kernel_timespec case, but that looks like a bit
> > > > > more fun!
> > > > >
> > > > > Dave
> > > >
> > > > I thought Stefanha had fixed this bug, and we were just waiting for a
> > > > new alpine rootfs/image with that fixed.
> > > > Is that correct?
> > >
> > > I didn't fix the liburing __kernel_timespec issue on alpine Linux. It's
> > > probably a packaging bug and I gave Dave the email address of the
> > > package maintainer. I'm not sure if the package maintainer has been
> > > contacted or released a fixed liburing package.
> >
> > It was prety easy to bisect the problem with liburing so I filed a
> > bug pointing to the fix needed:
> >
> > https://gitlab.alpinelinux.org/alpine/aports/-/issues/13813
>
> Alpine win the prize for quickest distro bug fix response. The liburing
> problem is now fixed in all current Alpine release streams, just minutes
> after I filed the above bug.
Awesome, thank you for identifying the issue and filing the issue!
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-05-16 16:18 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 8:33 [PULL 00/16] migration queue Dr. David Alan Gilbert (git)
2022-05-10 8:33 ` [PULL 01/16] tests: fix encoding of IP addresses in x509 certs Dr. David Alan Gilbert (git)
2022-05-10 8:33 ` [PULL 02/16] tests: add more helper macros for creating TLS " Dr. David Alan Gilbert (git)
2022-05-10 8:33 ` [PULL 03/16] tests: add migration tests of TLS with PSK credentials Dr. David Alan Gilbert (git)
2022-05-10 8:33 ` [PULL 04/16] tests: add migration tests of TLS with x509 credentials Dr. David Alan Gilbert (git)
2022-05-10 8:33 ` [PULL 05/16] tests: convert XBZRLE migration test to use common helper Dr. David Alan Gilbert (git)
2022-05-10 8:33 ` [PULL 06/16] tests: convert multifd migration tests " Dr. David Alan Gilbert (git)
2022-05-10 8:33 ` [PULL 07/16] tests: add multifd migration tests of TLS with PSK credentials Dr. David Alan Gilbert (git)
2022-05-10 8:33 ` [PULL 08/16] tests: add multifd migration tests of TLS with x509 credentials Dr. David Alan Gilbert (git)
2022-05-10 8:33 ` [PULL 09/16] tests: ensure migration status isn't reported as failed Dr. David Alan Gilbert (git)
2022-05-10 8:33 ` [PULL 10/16] QIOChannel: Add flags on io_writev and introduce io_flush callback Dr. David Alan Gilbert (git)
2022-05-10 8:33 ` [PULL 11/16] QIOChannelSocket: Implement io_writev zero copy flag & io_flush for CONFIG_LINUX Dr. David Alan Gilbert (git)
2022-05-10 8:33 ` [PULL 12/16] migration: Add zero-copy-send parameter for QMP/HMP for Linux Dr. David Alan Gilbert (git)
2022-05-10 8:33 ` [PULL 13/16] migration: Add migrate_use_tls() helper Dr. David Alan Gilbert (git)
2022-05-10 8:33 ` [PULL 14/16] multifd: multifd_send_sync_main now returns negative on error Dr. David Alan Gilbert (git)
2022-05-10 8:33 ` [PULL 15/16] multifd: Send header packet without flags if zero-copy-send is enabled Dr. David Alan Gilbert (git)
2022-05-10 8:33 ` [PULL 16/16] multifd: Implement zero copy write in multifd migration (multifd-zero-copy) Dr. David Alan Gilbert (git)
2022-05-10 9:58 ` [PULL 00/16] migration queue Dr. David Alan Gilbert
2022-05-10 10:19 ` Daniel P. Berrangé
2022-05-10 10:43 ` Dr. David Alan Gilbert
2022-05-11 3:40 ` Leonardo Bras Soares Passos
2022-05-11 8:55 ` Dr. David Alan Gilbert
2022-05-13 6:28 ` Leonardo Bras Soares Passos
2022-05-16 8:18 ` Dr. David Alan Gilbert
2022-05-16 8:51 ` Stefan Hajnoczi
2022-05-16 9:40 ` Daniel P. Berrangé
2022-05-16 10:09 ` Daniel P. Berrangé
2022-05-16 15:30 ` Stefan Hajnoczi [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-09 15:02 Dr. David Alan Gilbert (git)
2020-10-26 16:19 Dr. David Alan Gilbert (git)
2020-10-26 16:39 ` no-reply
2020-10-26 16:52 ` Dr. David Alan Gilbert
2020-10-27 11:28 ` Peter Maydell
2020-10-31 16:12 ` Christian Schoenebeck
2020-10-31 17:26 ` Peter Maydell
2020-10-31 17:46 ` Peter Xu
2020-10-31 19:10 ` Christian Schoenebeck
2020-11-01 10:17 ` Christian Schoenebeck
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=YoJt/6S0t3xFS6b/@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=leobras@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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.