From: "andy@kernel.org" <andy@kernel.org>
To: YE Chengfeng <cyeaa@connect.ust.hk>
Cc: Kent Gibson <warthog618@gmail.com>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"brgl@bgdev.pl" <brgl@bgdev.pl>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gpio: gpiolib-cdev: Fix potential &lr->wait.lock deadlock issue
Date: Mon, 26 Jun 2023 14:13:45 +0300 [thread overview]
Message-ID: <ZJly6YWZsI3ItNRM@smile.fi.intel.com> (raw)
In-Reply-To: <3C977550-9829-4A6F-A5CA-04C938D77693@connect.ust.hk>
On Mon, Jun 26, 2023 at 10:38:53AM +0000, YE Chengfeng wrote:
> > 1) do you have any warning/oops/etc to show the real case?
> > 2) shouldn't we annotate with respective lockdep asserts this code?
> The bugs were detected by an experimental static code analyzer that I am
> implementing. I don't have input to trigger it, so I manually review the
> report and then send the ones I believe to be true to you. Perhaps next
> time I should mention this while sending the patch.
This you have to mention in the submission.
https://docs.kernel.org/process/researcher-guidelines.html
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-06-26 11:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 14:45 [PATCH] gpio: gpiolib-cdev: Fix potential &lr->wait.lock deadlock issue YE Chengfeng
2023-06-26 6:53 ` Andy Shevchenko
2023-06-26 7:23 ` Kent Gibson
2023-06-26 10:38 ` YE Chengfeng
2023-06-26 11:13 ` andy [this message]
2023-06-26 15:50 ` Bartosz Golaszewski
2023-06-26 16:51 ` YE Chengfeng
2023-06-27 1:43 ` Kent Gibson
2023-06-27 11:47 ` Bartosz Golaszewski
2023-06-27 11:57 ` Kent Gibson
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=ZJly6YWZsI3ItNRM@smile.fi.intel.com \
--to=andy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=cyeaa@connect.ust.hk \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=warthog618@gmail.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;
as well as URLs for NNTP newsgroup(s).