All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajdeep Malakar <rajdeepm.dev@gmail.com>
To: ell@lists.linux.dev
Subject: Segmentation Fault in iwd with ell 0.68 Due to l_netlink_send()
Date: Mon, 26 Aug 2024 23:44:13 +0530	[thread overview]
Message-ID: <d16d043c-aa5c-4fb8-8df6-8c109c6239bf@gmail.com> (raw)


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

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.

Issue Details:

- Function Causing Segfault: l_netlink_send()
- Error: SIGSEGV (Segmentation Fault)
- Library Path: /usr/lib/libell.so.0
- System: Arch Linux x86-64

Reproduction Steps:

1. Upgrade ell from version 0.67 to 0.68.
2. Start iwd.
3. Observe the segmentation fault.

I confirmed this issue using gdb, which indicates that l_netlink_send() 
in the ell library is causing the segmentation fault.

Reverting to ell version 0.67 resolves the issue without causing a 
segmentation fault.

Since there have been no updates or commits in the repository since the 
release, I wanted to bring this to your attention. This might be a 
specific problem with the recent version, and any insights or solutions 
would be greatly appreciated.

Please let me know if additional information is needed or if there are 
any known issues with this version.

---
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 18:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26 18:14 Rajdeep Malakar [this message]
2024-08-26 18:46 ` Segmentation Fault in iwd with ell 0.68 Due to l_netlink_send() Denis Kenzior
2024-08-26 18:55   ` Rajdeep Malakar
2024-08-26 19:06     ` Rajdeep Malakar
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=d16d043c-aa5c-4fb8-8df6-8c109c6239bf@gmail.com \
    --to=rajdeepm.dev@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.