All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: Rajdeep Malakar <rajdeepm.dev@gmail.com>, ell@lists.linux.dev
Subject: Re: Segmentation Fault in iwd with ell 0.68 Due to l_netlink_send()
Date: Mon, 26 Aug 2024 14:20:20 -0500	[thread overview]
Message-ID: <83a579fd-1f2a-403d-a3e4-e447b3885d62@gmail.com> (raw)
In-Reply-To: <5b232f87-2fd9-445f-8650-66a05ad18217@gmail.com>

Hi Rajdeep,

> 
> So, I compiled ell with a bit more info:
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff7f3e17c in l_netlink_send (netlink=0x55555563bc60, message=0x12, 
> function=0x0, user_data=0x555555651e50, destroy=0x10) at ell/netlink.c:413
> 413             if (unlikely(message->nest_level))
> 
> a bit more backtrace:
> 
> #0  0x00007ffff7f3e17c in l_netlink_send (netlink=0x55555563bc60, message=0x12, 
> function=0x0, user_data=0x555555651e50, destroy=0x10) at ell/netlink.c:413
> #1  0x000055555556d53d in ?? ()
> #2  0x00005555555ae380 in ?? ()
> #3  0x00007ffff7f40014 in process_unicast (genl=<optimized out>, 
> nlmsg=0x7fffffffc140) at ell/genl.c:860
> #4  received_data (io=<optimized out>, user_data=0x55555563b8b0) at ell/genl.c:972
> #5  0x00007ffff7f3c2ac in io_callback (fd=<optimized out>, events=1, 
> user_data=0x55555563b800) at ell/io.c:105
> #6  0x00007ffff7f3b495 in l_main_iterate (timeout=<optimized out>) at 
> ell/main.c:461
> #7  0x00007ffff7f3b55c in l_main_run () at ell/main.c:508
> #8  l_main_run () at ell/main.c:490
> #9  0x00007ffff7f3b77b in l_main_run_with_signal (callback=<optimized out>, 
> user_data=0x0) at ell/main.c:630
> #10 0x000055555555fd13 in ?? ()
> #11 0x00007ffff7d0ae08 in ?? () from /usr/lib/libc.so.6
> #12 0x00007ffff7d0aecc in __libc_start_main () from /usr/lib/libc.so.6
> #13 0x0000555555560575 in ?? ()
> 
> Let me know if you need more info.

I suspect that this is a binary compatibility problem.  ell API is not stable, 
so ell + iwd are released in tandem.  ell 0.68 breaks certain netlink APIs.  iwd 
2.19 requires ell 0.67.  iwd 2.20 will require ell 0.68, etc.

Regards,
-Denis


  reply	other threads:[~2024-08-26 19:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26 18:14 Segmentation Fault in iwd with ell 0.68 Due to l_netlink_send() Rajdeep Malakar
2024-08-26 18:46 ` Denis Kenzior
2024-08-26 18:55   ` Rajdeep Malakar
2024-08-26 19:06     ` Rajdeep Malakar
2024-08-26 19:20       ` Denis Kenzior [this message]
2024-08-26 19:27         ` Rajdeep Malakar

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=83a579fd-1f2a-403d-a3e4-e447b3885d62@gmail.com \
    --to=denkenz@gmail.com \
    --cc=ell@lists.linux.dev \
    --cc=rajdeepm.dev@gmail.com \
    /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.