From: Greg KH <gregkh@linuxfoundation.org>
To: Simon Kaegi <simon.kaegi@gmail.com>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev,
Bobby Eshleman <bobby.eshleman@bytedance.com>,
Stefano Garzarella <sgarzare@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Sasha Levin <sashal@kernel.org>,
jpiotrowski@linux.microsoft.com
Subject: Re: [REGRESSION] vsocket timeout with kata containers agent 3.2.0 and kernel 6.1.63
Date: Mon, 11 Dec 2023 07:46:12 +0100 [thread overview]
Message-ID: <2023121156-giblet-thumb-037f@gregkh> (raw)
In-Reply-To: <CACW2H-4FpZAizkp+U1aS94V_ODn8NUd1ta27BAz_zh0wo63_rQ@mail.gmail.com>
On Sun, Dec 10, 2023 at 11:05:37PM -0500, Simon Kaegi wrote:
> #regzbot introduced v6.1.62..v6.1.63
> #regzbot introduced: baddcc2c71572968cdaeee1c4ab3dc0ad90fa765
>
> We hit this regression when updating our guest vm kernel from 6.1.62 to
> 6.1.63 -- bisecting, this problem was introduced
> in baddcc2c71572968cdaeee1c4ab3dc0ad90fa765 -- virtio/vsock: replace
> virtio_vsock_pkt with sk_buff --
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.63&id=baddcc2c71572968cdaeee1c4ab3dc0ad90fa765
>
> We're getting a timeout when trying to connect to the vsocket in the
> guest VM when launching a kata containers 3.2.0 agent. We haven't done
> much more to understand the problem at this point.
>
> We can reproduce 100% of the time but don't currently have a simple
> reproducer as the problem was found in our build service which uses
> kata-containers (with cloud-hypervisor).
>
> We have not checked the mainline as we currently are tied to 6.1.x.
What is "tieing" you to the old 6.1.y tree?
Also, can you try 6.1.66? Numerous fixes have gone into there as well.
thanks,
greg k-h
next prev parent reply other threads:[~2023-12-11 6:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 4:05 [REGRESSION] vsocket timeout with kata containers agent 3.2.0 and kernel 6.1.63 Simon Kaegi
2023-12-11 6:46 ` Greg KH [this message]
2023-12-11 8:38 ` Stefano Garzarella
2023-12-11 14:20 ` Simon Kaegi
2023-12-11 15:23 ` Stefano Garzarella
2023-12-15 9:38 ` Linux regression tracking #update (Thorsten Leemhuis)
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=2023121156-giblet-thumb-037f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bobby.eshleman@bytedance.com \
--cc=davem@davemloft.net \
--cc=jpiotrowski@linux.microsoft.com \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=sgarzare@redhat.com \
--cc=simon.kaegi@gmail.com \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox