> > while (e->state != SD_EVENT_FINISHED) {
> > r = sd_event_run(e, (uint64_t) -1);
> >
> > But since e->state is changed by another thread it
Well..then the game is up because sd-bus does not claim to be thread
safe or even aspires to be.. accessing e from different threads will
cause unspecified behaviour.
In any case this patch is not quite what is needed to make it safe.
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: EXT: sdbus_event loop state mark as volatile?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: EXT: sdbus_event loop state mark as volatile?
- From: Cristian Rodríguez <crrodriguez@xxxxxxxxxxxx>
- Date: Mon, 9 Sep 2019 13:08:03 -0300
- Cc: "systemd-devel@xxxxxxxxxxxxxxxxxxxxx" <systemd-devel@xxxxxxxxxxxxxxxxxxxxx>
- In-reply-to: <5C597597-7E6C-476D-99BA-AFC1D8E838C3@ge.com>
- References: <20190905104612.0102c281@hermes.lan> <5C597597-7E6C-476D-99BA-AFC1D8E838C3@ge.com>
- References:
- sdbus_event loop state mark as volatile?
- From: Stephen Hemminger
- Re: EXT: sdbus_event loop state mark as volatile?
- From: Ray, Ian (GE Healthcare)
- sdbus_event loop state mark as volatile?
- Prev by Date: exceeding match limit via sd_bus_add_match
- Next by Date: host0 virtual link suddenly default down in systemd-nspawn container
- Previous by thread: Re: EXT: sdbus_event loop state mark as volatile?
- Next by thread: Re: sdbus_event loop state mark as volatile?
- Index(es):
 |