On 25 November 2014 at 17:57, Ted Unangst <t...@tedunangst.com> wrote: > On Tue, Nov 25, 2014 at 17:35, Mike Belopuhov wrote: >> On Tue, Nov 25, 2014 at 13:11 +0100, Vincent Gross wrote: >>> Hi tech@, >>> >>> I've been using iked for some weeks to tunnel my laptop to home over 3G. >>> Sunday I upgraded my laptop to the latest snapshot; previous upgrade was >>> about 2 or 3 weeks ago. When I started iked, it crashed randomly, as in >>> one time it runs just fine and completes the handshake, the other it >>> crashes before even sending the first packet. >>> >>> I ran "ktrace -di /sbin/iked" and kdump'd the resulting file. Of the 5 >>> processes, 4 finished by calling exit(0), one was terminated on a >>> SIGSEGV. As it is also the only one that do stuff on /var/run/iked.sock, >>> it is the control process. I repeated the above ktrace 4 times and got >>> consistent results: SIGSEGV'd control process. >>> >>> I'll keep the hunt going, but I am not sure how long this will take nor >>> how much time I'll have to spare, so here is the control process kdump. >>> >>> Cheers, >>> >>> -- >>> Vincent >>> >> >> señior pedro@ was kind enough to send a potential fix for this. >> this will be commited soon. > > This looks a bit weird. What about >
nah. at least you see what's your iovcnt is every time you fill in an iov.
