Re: Bad signalling message

On Tue, Oct 16, 2012 at 01:11:34PM +0200, Lennart Müller wrote: [...]

Hi Pablo, thanks for the patch. msgb_free(msg); causes signal 6, I tried the following and it works, but might cause a memory leak...

   if (e1i_ts->line->ops->sign_link(msg) < 0) {
       /* Don't close the signalling link if the upper layers report
        * an error, that's too strict.
        */
       LOGP(DLINP, LOGL_ERROR, "Bad signalling message,"
           "sign_link returned error\n");
       ret = -EINVAL;
       //msgb_free(msg);
       return(ret);

I see. I guess you were hitting SIGABRT also before the patch then.

New patch attached. If you're OK with it, I'll push it to git.