From: Sander Eikelenboom <linux@eikelenboom.it>
To: Andrew Cooper <Andrew.Cooper3@citrix.com>,
Ross Lagerwall <ross.lagerwall@citrix.com>,
Juergen Gross <jgross@suse.com>,
Xen-devel <xen-devel@lists.xen.org>, Paul Durrant <paul@xen.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: Xen + linux 6.1.0-rc8, network to guest VM not working after commit ad7f402ae4f466647c3a669b8a6f3e5d4271c84a fixing XSA-423
Date: Thu, 8 Dec 2022 19:31:40 +0100 [thread overview]
Message-ID: <c5dc1c91-dd32-e233-6029-10b175fc1eff@eikelenboom.it> (raw)
In-Reply-To: <56054539-4a02-5310-b93f-6baacaf8e007@citrix.com>
On 08/12/2022 00:00, Andrew Cooper wrote:
> On 07/12/2022 21:42, Sander Eikelenboom wrote:
>> Hi Ross / Juergen,
>>
>> I just updated my linux kernel to the latest of Linus his tree which
>> included commit ad7f402ae4f466647c3a669b8a6f3e5d4271c84a fixing XSA-423.
>>
>> Unfortunately when using this kernel I can't SSH anymore into the Xen
>> guest I start, but I don't see any apparent failures either.
>> A straight revert of the commit
>> ad7f402ae4f466647c3a669b8a6f3e5d4271c84a makes networking function
>> normally again.
>>
>> I have added some of the logging below, perhaps it at gives some idea
>> off the state around the Xen network front and backend.
>>
>> Any ideas or a test patch that I could run to shed some more light on
>> what is going on ?
>
> XSA-423 was buggy. Fix and discussion at:
>
> https://lore.kernel.org/xen-devel/681773dd-6264-63ac-a3b5-a9182b9e0cc1@suse.com/T/#t
>
> ~Andrew
Thanks for the pointer Andrew, that fix works for me as well!
What a difference a few characters can make :)
--
Sander
prev parent reply other threads:[~2022-12-08 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 21:42 Sander Eikelenboom
2022-12-07 23:00 ` Andrew Cooper
2022-12-08 18:31 ` Sander Eikelenboom [this message]
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=c5dc1c91-dd32-e233-6029-10b175fc1eff@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=Andrew.Cooper3@citrix.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@xen.org \
--cc=ross.lagerwall@citrix.com \
--cc=xen-devel@lists.xen.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
all inboxes | Powered by JetHome®