[13:43] this bug is, err, bugging me [13:46] it looks like four jobs were started from the same event [13:46] and the one that made it then freed that event, despite the refcount [14:03] sadmac2: oh, I'm going to beat you [14:19] Keybuk: what's going on? Give me the 1 hour of sleep version. [14:24] you know that "rewind the data and upstart crashes" bug? [14:27] yes [14:27] I think it's caused by a Fedora patch [14:28] which? [14:29] not sure yet [14:29] but I suspect the re-exec one [14:30] well I didn't write that, so its all good [14:30] mostly good... [14:31] just need to prove it [14:32] basically an inviolate constraint is being violated ;) [15:55] hmm [15:55] I can't see anything about your patch that might do that, sadly [15:56] have you reproduced this thing? [16:05] nope [17:18] though his log just made me go "HUH" [17:18] I like following state machines on paper [17:18] it's SO MUCH FUN [17:29] :-) [17:35] * Keybuk now has ice cream [17:42] I have reached the event that kills everything [17:43] I can see it on the event queue [17:43] (the bit of paper on the rhs of my desk) [18:06] Handling started event [18:06] ? goal changed from stop to start [18:06] ? state changed from waiting to starting [18:06] ? respawning too fast, stopped [18:06] ? respawning too fast, stopped [18:06] ? goal changed from start to stop [18:06] ? state changed from starting to waiting [18:06] ... wonder whether that could be it [18:06] the double "respawning too fast" is kinda odd [18:06] but, more than that, the respawn detection is the one thing that could be broken by the date spooling backwards [18:19] kids [18:19] remember [18:19] time(NULL) is not monotonic [18:28] https://bugs.edge.launchpad.net/upstart/+bug/388873/comments/26 [18:37] gnnnrgh [18:37] this is a bug [18:38] Keybuk: as opposed to? [18:39] as in, I can now, following the code, see how it goes wrong :) [18:49] oic [18:49] can you /fix/ it though? [18:51] first I write a test case ;) [18:51] and forward port that to 0.5 to check [18:51] I'm pretty sure 0.5 is expressly not vulnerable, because I totally rewrote the event queue there [18:51] interestingly, I appear to have rewritten it to exactly avoid this issue [18:51] will check the test cases there to see whether I already hit this bug, or a similar one, and didn't realise === Keybuk changed the topic of #upstart to: Upstart 0.5.2 "Something, something, something, D-Bus" | Upstart 0.3.11 "For Friday, June 19th 2009, I'm Jon Masters" | http://upstart.ubuntu.com/