Skip to content
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

device: Ensure we have sysfs path before comparing. #2834

Merged
merged 1 commit into from
Mar 14, 2016

Conversation

coling
Copy link

@coling coling commented Mar 14, 2016

In some cases we do not have a udev device when setting up a unit
(certainly the code gracefully handles this). However, we do
then go on to compare the path via path_equal which will assert
if a null value is passed in.

See https://bugs.mageia.org/show_bug.cgi?id=17766

Not sure if this is the correct fix, but it avoids the crash

In some cases we do not have a udev device when setting up a unit
(certainly the code gracefully handles this). However, we do
then go on to compare the path via path_equal which will assert
if a null value is passed in.

See https://bugs.mageia.org/show_bug.cgi?id=17766

Not sure if this is the correct fix, but it avoids the crash
@evverx
Copy link
Member

evverx commented Mar 14, 2016

#7  0x000055fd15d0c28b in mount_load_proc_self_mountinfo (m=m@entry=0x55fd15f9a320, set_flags=set_flags@entry=true) at src/core/mount.c:1537

Seems like #2730 (comment)

#2730 (comment)

That said this looks a bit weird that a side effect of unit_add_dependency_by_name(u, ...) is to invalidate 'u'. Note sure that all callers are prepared to that...

@keszybz keszybz merged commit 5e1558f into systemd:master Mar 14, 2016
keszybz added a commit that referenced this pull request Mar 14, 2016
@keszybz
Copy link
Member

keszybz commented Mar 14, 2016

The change looks "obviously correct", so I merged the commit. I took the liberty though to change sysfs to dev in the condition, it is equivalent, but shows the intent more clearly for me.

@ghost
Copy link

ghost commented Nov 4, 2017

Intermittently, I am getting a lot of time out errors, generated by Conky - thus:

Failed to retrieve unit: Connection timed out
Failed to get properties: Connection timed out
Failed to retrieve unit: Connection timed out
Failed to get properties: Connection timed out
Failed to retrieve unit: Connection timed out
Failed to get properties: Connection timed out
Failed to retrieve unit: Connection timed out
Failed to get properties: Connection timed out
Failed to retrieve unit: Connection timed out
Failed to get properties: Connection timed out
Failed to retrieve unit: Connection timed out
Failed to get properties: Connection timed out
Failed to retrieve unit: Connection timed out
Failed to get properties: Connection timed out
Failed to retrieve unit: Connection timed out
Failed to get properties: Connection timed out
Failed to retrieve unit: Connection timed out
Failed to get properties: Connection timed out

Should I open a new issue?

Mint 18.2 x64 Cinnamon

@keszybz
Copy link
Member

keszybz commented Nov 5, 2017

Yes, please open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

None yet

4 participants