Re: [PATCH] kobject: Safe return of kobject_get_path with NULL

From: Christian Löhle
Date: Thu Jun 24 2021 - 02:42:52 EST

Hey Greg,

>> Prevent NULL dereference within get_kobj_path_length
>> Calling kobject_get_path could provoke a NULL dereference
>> if NULL was passed. while fill_kobj_path will return
>> with a sane 0 for NULL, kobjet_get_path_length did not.
>Who passes NULL into that function?  Shouldn't that be fixed first?

It seems to me like here specifically it was a sd_open on some no longer
existing device. I agree, but could not find a fix for that, and even if, it might
not have been in the current tree.
But when looking at the kobject code it felt like it was meant to be safe for
NULL, (like any parent in the tree can be NULL), but the do while does hide that
a bit.
So is it not meant to be safe?
I will try to find the sd_open issue some more, but cannot reproduce the issue
consistently enough right now.

>Pleaase always run your patches through so you do not get
>maintainers asking you to use

I did, so please tell me what part bothers you, so I can get that fixed, either in v2
or maybe even in
(Only thing I spotted now is the kobjet typo)

Hyperstone GmbH | Line-Eid-Strasse 3 | 78467 Konstanz
Managing Directors: Dr. Jan Peter Berns.
Commercial register of local courts: Freiburg HRB381782