All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Race condition on device add hanling in xl devd
Date: Mon, 17 Dec 2018 13:23:15 +0100	[thread overview]
Message-ID: <20181217122315.GC23474@mail-itl> (raw)
In-Reply-To: <20181217121855.zsrn6fvliz4f5yul@mac>


[-- Attachment #1.1: Type: text/plain, Size: 1801 bytes --]

On Mon, Dec 17, 2018 at 01:18:55PM +0100, Roger Pau Monné wrote:
> On Mon, Dec 17, 2018 at 01:00:01PM +0100, Marek Marczykowski-Górecki wrote:
> > On Mon, Dec 17, 2018 at 10:40:59AM +0100, Roger Pau Monné wrote:
> > > On Sun, Dec 16, 2018 at 02:47:43AM +0100, Marek Marczykowski-Górecki wrote:
> > > > A workaround could be implemented in hotplug script itself - wait for
> > > > the device there. I'm not sure how proper solution could look like. Some
> > > > synchronization between xl devd and the kernel (like xl devd monitoring
> > > > uevents)?
> > > 
> > > There's already a synchronization mechanism, libxl waits for the
> > > backend to switch to state 2 (XenbusStateInitWait) before running the
> > > hotplug scripts [0].
> > > 
> > > Maybe netback sets state 2 before creating the backend device?
> > > 
> > > It looks to me like the backend needs to be sure everything needed by
> > > the hotplug script is in place before switching to state 2.
> > 
> > I've done some more tests and I think that's something else. I've added
> > a loop waiting for /sys/class/net/$vif to a hotplug script, but it timed
> > out (5s). I don't see _any_ kernel messages related to the device.
> > 
> > It may be some bug in nested virtualization in KVM...
> 
> In your message you said you have also observed this behavior when
> running on bare metal, so it's likely not related to nested
> virtualization?

Yes, but on bare metal is so hard to reproduce (like 0.1% or even less
startups), I'm not really sure if that was the same problem, as the
problem doesn't leave that much logs...

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-12-17 12:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-16  1:47 Race condition on device add hanling in xl devd Marek Marczykowski-Górecki
2018-12-17  9:40 ` Roger Pau Monné
2018-12-17 12:00   ` Marek Marczykowski-Górecki
2018-12-17 12:18     ` Roger Pau Monné
2018-12-17 12:23       ` Marek Marczykowski-Górecki [this message]
2018-12-17 13:05         ` Roger Pau Monné
2018-12-17 13:11           ` Paul Durrant
2018-12-17 14:32             ` Roger Pau Monné
2018-12-17 14:42               ` Paul Durrant
2018-12-17 16:09                 ` Roger Pau Monné
2019-02-24 23:14                   ` Marek Marczykowski-Górecki
2019-02-28 10:08                     ` Roger Pau Monné
2019-02-28 12:38                       ` Marek Marczykowski-Górecki
2018-12-17 13:23           ` Marek Marczykowski-Górecki
2018-12-17 14:44             ` Roger Pau Monné

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=20181217122315.GC23474@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --cc=roger.pau@citrix.com \
    --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 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.