All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajdeep Malakar <rajdeepm.dev@gmail.com>
To: Denis Kenzior <denkenz@gmail.com>, ell@lists.linux.dev
Subject: Re: Segmentation Fault in iwd with ell 0.68 Due to l_netlink_send()
Date: Tue, 27 Aug 2024 00:36:06 +0530	[thread overview]
Message-ID: <5b232f87-2fd9-445f-8650-66a05ad18217@gmail.com> (raw)
In-Reply-To: <b7a1d7fd-a42a-48f0-8c1f-c5cc19b15a9f@gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 2872 bytes --]

On 27/08/24 00:25, Rajdeep Malakar wrote:
Hi Denis,

> Hi Denis,
> 
> On 27/08/24 00:16, Denis Kenzior wrote:
>> Hi Rajdeep,
>>
>> On 8/26/24 1:14 PM, Rajdeep Malakar wrote:
>>> Hi,
>>>
>>> I’m encountering a segmentation fault in iwd after upgrading the ell 
>>> library from version 0.67 to 0.68. The issue seems to be related to 
>>> the l_netlink_send() function in the ell library.
>>
>> Thanks for the report.  Do you have a backtrace you can share by any 
>> chance?
>>
>> Regards,
>> -Deni
> Unfortunately, the `libell.so` I have (from Arch's [extra-testing] repo) 
> wasn't compiled with debuginfo, so all the backtrace I have is:
> 
> #0  0x00007ffff7f22de6 in l_netlink_send () from /usr/lib/libell.so.0
> #1  0x000055555556d53d in ?? ()
> #2  0x00005555555ae380 in ?? ()
> #3  0x00007ffff7f25b95 in ?? () from /usr/lib/libell.so.0
> #4  0x00007ffff7f203cb in ?? () from /usr/lib/libell.so.0
> #5  0x00007ffff7f20655 in l_main_iterate () from /usr/lib/libell.so.0
> #6  0x00007ffff7f20ace in l_main_run () from /usr/lib/libell.so.0
> #7  0x00007ffff7f223a4 in l_main_run_with_signal () from 
> /usr/lib/libell.so.0
> #8  0x000055555555fd13 in ?? ()
> #9  0x00007ffff7d0ee08 in ?? () from /usr/lib/libc.so.6
> #10 0x00007ffff7d0eecc in __libc_start_main () from /usr/lib/libc.so.6
> #11 0x0000555555560575 in ?? ()
> 
> I will try to compile it with debuginfo and get the backtrace.
> 

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.
-- 
regards,
rajdeep


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 669 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2024-08-26 19:06 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 [this message]
2024-08-26 19:20       ` Denis Kenzior
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=5b232f87-2fd9-445f-8650-66a05ad18217@gmail.com \
    --to=rajdeepm.dev@gmail.com \
    --cc=denkenz@gmail.com \
    --cc=ell@lists.linux.dev \
    /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.