From: Juergen Gross <jgross@suse.com>
To: Dominique Martinet <asmadeus@codewreck.org>,
Alexander Merritt <alexander@edera.dev>
Cc: v9fs@lists.linux.dev, linux-kernel@vger.kernel.org,
xen-devel@lists.xenproject.org,
Eric Van Hensbergen <ericvh@kernel.org>,
Latchesar Ionkov <lucho@ionkov.net>,
Christian Schoenebeck <linux_oss@crudebyte.com>,
Simon Horman <horms@kernel.org>, Alex Zenla <alex@edera.dev>,
Ariadne Conill <ariadne@ariadne.space>
Subject: Re: [PATCH] 9p/xen: fix init sequence
Date: Thu, 21 Nov 2024 13:27:52 +0100 [thread overview]
Message-ID: <a15245c9-9be6-4de7-84a8-693931b1b3aa@suse.com> (raw)
In-Reply-To: <Zz8mWwLQBNq6eopG@codewreck.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 766 bytes --]
On 21.11.24 13:23, Dominique Martinet wrote:
> Alexander Merritt wrote on Tue, Nov 19, 2024 at 09:16:33PM +0000:
>> From: Alex Zenla <alex@edera.dev>
>>
>> Large amount of mount hangs observed during hotplugging of 9pfs devices. The
>> 9pfs Xen driver attempts to initialize itself more than once, causing the
>> frontend and backend to disagree: the backend listens on a channel that the
>> frontend does not send on, resulting in stalled processing.
>>
>> Only allow initialization of 9p frontend once.
>
> I'm not familiar with the xen bringup so I don't understand how the
> patch guarantees this -- otherend_changed calls are guaranted to be
> seralized for a given frontend?
Yes. They are all executed by a single kernel thread.
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
prev parent reply other threads:[~2024-11-21 12:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 21:16 Alexander Merritt
2024-11-21 12:00 ` Jürgen Groß
2024-11-21 12:23 ` Dominique Martinet
2024-11-21 12:27 ` Juergen Gross [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=a15245c9-9be6-4de7-84a8-693931b1b3aa@suse.com \
--to=jgross@suse.com \
--cc=alex@edera.dev \
--cc=alexander@edera.dev \
--cc=ariadne@ariadne.space \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=v9fs@lists.linux.dev \
--cc=xen-devel@lists.xenproject.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®