-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
systemd-network segfault #32254
Comments
|
It's probably a duplicate of #32247 |
Oh it must be! I didn't find that in a search because I looked for "systemd-network segfault", not systemd-networkd. Oops. |
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
Apr 12, 2024
Fixes a bug introduced by be8e933 (v255). Fixes systemd#32247. Fixes systemd#32254.
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
Apr 15, 2024
Fixes a bug introduced by be8e933 (v255). Fixes systemd#32247. Fixes systemd#32254.
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
Apr 26, 2024
Fixes a bug introduced by be8e933 (v255). Fixes systemd#32247. Fixes systemd#32254. (cherry picked from commit 632d321)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
systemd version the issue has been seen with
255.4
Used distribution
Arch Linux
Linux kernel version used
6.8.4-arch1-1
CPU architectures issue was seen on
x86_64
Component
systemd-networkd
Expected behaviour you didn't see
No segfaults
Unexpected behaviour you saw
I was trying out different qdisc settings earlier today. Just now I noticed a
systemd-networksegfault in my logs.coredumpctl gdbshows it's an infinite recursion betweentclass_drop()andqdisc_drop():Steps to reproduce the problem
I haven't been able to reproduce it since, but the commands I was running at the time were like this:
Additional program output to the terminal or log subsystem illustrating the issue
The text was updated successfully, but these errors were encountered: