[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f23c038b2b586a45a8b3c757495d5bb51ee4ac7e.camel@sipsolutions.net>
Date: Tue, 18 Apr 2023 10:36:14 +0200
From: Johannes Berg <johannes@...solutions.net>
To: yingsha xu <ysxu@...t.edu.cn>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Jiri Benc <jbenc@...e.cz>,
"John W. Linville" <linville@...driver.com>
Cc: hust-os-kernel-patches@...glegroups.com,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] net: mac80211: use IS_ERR to check return value
On Sun, 2023-04-16 at 16:30 +0800, yingsha xu wrote:
> According to the annotation of function debugfs_create_fs, if
> an error occurs, ERR_PTR(-ERROR) will be returned instead of
> a null pointer or zero value.
>
> Fix it by using IS_ERR().
I don't this this is right, or fixed anything ...
If debugfs indeed returned an ERR_PTR() value, then the later debugfs
adds will do nothing.
Since it doesn't look like debugfs_create_dir() can actually return NULL
these days (not sure it ever could), I guess we can even remove the
check.
But you could've just read the comment there too, to know what the NULL
check was about ...
johannes
Powered by blists - more mailing lists