From: Michael Brown <mbrown@fensystems.co.uk>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: paul@xen.org, xen-devel@lists.xenproject.org,
netdev@vger.kernel.org, wei.liu@kernel.org, pdurrant@amazon.com
Subject: Re: [PATCH] xen-netback: Check for hotplug-status existence before watching
Date: Mon, 10 May 2021 20:06:55 +0100 [thread overview]
Message-ID: <21f38a92-c8ae-12a7-f1d8-50810c5eb088@fensystems.co.uk> (raw)
In-Reply-To: <YJmBDpqQ12ZBGf58@mail-itl>
On 10/05/2021 19:53, Marek Marczykowski-Górecki wrote:
> On Mon, May 10, 2021 at 07:47:01PM +0100, Michael Brown wrote:
>> That doesn't sound plausible to me. In the setup as you describe, how is
>> the kernel expected to differentiate between "hotplug script has not yet
>> created the node" and "hotplug script does not exist and will therefore
>> never create any node"?
>
> Is the later valid at all? From what I can see in the toolstack, it
> always sets some hotplug script (if not specified explicitly - then
> "vif-bridge"),
I don't see any definitive documentation around that so I can't answer
for sure. It's probably best to let one of the Xen guys answer that.
If you have a suggested patch, I'm happy to test that it doesn't
reintroduce the regression bug that was fixed by this commit.
Michael
next prev parent reply other threads:[~2021-05-10 19:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 18:25 xen-netback hotplug-status regression bug Michael Brown
2021-04-13 7:12 ` Paul Durrant
2021-04-13 10:48 ` Michael Brown
2021-04-13 10:55 ` Paul Durrant
2021-04-13 15:14 ` Michael Brown
2021-04-13 15:25 ` [PATCH] xen-netback: Check for hotplug-status existence before watching Michael Brown
2021-04-13 19:12 ` Paul Durrant
2021-04-13 22:30 ` patchwork-bot+netdevbpf
2021-05-10 18:32 ` Marek Marczykowski-Górecki
2021-05-10 18:47 ` Michael Brown
2021-05-10 18:53 ` Marek Marczykowski-Górecki
2021-05-10 19:06 ` Michael Brown [this message]
2021-05-10 19:42 ` Marek Marczykowski-Górecki
2021-05-11 7:06 ` Durrant, Paul
2021-05-11 10:40 ` Marek Marczykowski-Górecki
2021-05-11 10:45 ` Marek Marczykowski-Górecki
2021-05-11 12:46 ` Durrant, Paul
2021-05-17 21:43 ` Marek Marczykowski-Górecki
2021-05-17 21:51 ` Michael Brown
2021-05-17 21:58 ` Marek Marczykowski-Górecki
2021-05-18 6:57 ` Paul Durrant
2021-05-18 9:18 ` Marek Marczykowski-Górecki
[not found] ` <887f9533f5c54bfabfbff7231eb99b08@EX13D32EUC003.ant.amazon.com>
[not found] ` <YKOMpXwcnr9QiXy8@mail-itl>
[not found] ` <2c23e102b6254e42877eb1e8fe68a4f7@EX13D32EUC003.ant.amazon.com>
2021-05-18 10:42 ` Marek Marczykowski-Górecki
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=21f38a92-c8ae-12a7-f1d8-50810c5eb088@fensystems.co.uk \
--to=mbrown@fensystems.co.uk \
--cc=marmarek@invisiblethingslab.com \
--cc=netdev@vger.kernel.org \
--cc=paul@xen.org \
--cc=pdurrant@amazon.com \
--cc=wei.liu@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).