From: Konrad Dybcio <konradybcio@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Yu Jiaoliang <yujiaoliang@vivo.com>,
Bjorn Andersson <andersson@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
opensource.kernel@vivo.com
Subject: Re: [PATCH v1] soc: qcom: pbs: Simplify with dev_err_probe()
Date: Thu, 5 Sep 2024 14:35:50 +0200 [thread overview]
Message-ID: <42cfe883-5411-4948-b36d-c0c3dd3d1294@kernel.org> (raw)
In-Reply-To: <6267a1fe-0073-4aca-ab19-a63a7565f116@stanley.mountain>
On 4.09.2024 8:55 PM, Dan Carpenter wrote:
> On Fri, Aug 30, 2024 at 05:31:14PM +0200, Konrad Dybcio wrote:
>>>
>>> There are a few things which we could do:
>>>
>>> 1) Returning -EPROBE_DEFER to an ioctl or something besides a probe()
>>> This is a bug right? -EPROBE_DEFER is basically kernel internal for probe()
>>> functions. It tried to write this but it was complicated so I gave up.
>>
>> Maybe call_tree.pl can somehow be used with an if name[-5:] == "probe"
>> or something along those lines..
>>
>
> I wrote the call_tree.pl script before I had the database. These days I tend to
> use the database instead.
>
> I've implemented this check but it only looks at ioctls. I'll test it tonight.
>
>>>
>>> 2) Printing an error message for -EPROBE_DEFER warnings
>>> I've written this check and I can test it tonight.
>>>
>
> I've done this. See the attached check and the dont_print.list file attached.
> The line numbers are based on linux next. The false positives from here are
> pretty harmless because calling dev_err_probe() is fine.
>
>>> 3) Not propagating the -EPROBE_DEFER returns
>>> This shouldn't be too hard to write.
>>>
>
> I've done this too. The false positives from this could be bad, because we only
> want to propagate -EPROBE_DEFER back from probe() functions.
>
> See propagate.list.
This is great work, thank you Dan!
Konrad
next prev parent reply other threads:[~2024-09-05 12:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 12:48 [PATCH v1] soc: qcom: pbs: Simplify with dev_err_probe() Yu Jiaoliang
2024-08-29 23:48 ` Konrad Dybcio
2024-08-30 8:08 ` Krzysztof Kozlowski
2024-08-30 10:03 ` Konrad Dybcio
2024-08-30 15:19 ` Dan Carpenter
2024-08-30 15:31 ` Konrad Dybcio
2024-09-04 18:55 ` Dan Carpenter
2024-09-05 12:35 ` Konrad Dybcio [this message]
2024-08-30 10:52 ` 于佼良
2024-08-30 10:57 ` Krzysztof Kozlowski
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=42cfe883-5411-4948-b36d-c0c3dd3d1294@kernel.org \
--to=konradybcio@kernel.org \
--cc=andersson@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=yujiaoliang@vivo.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox