linux-kernel - Re: [PATCH] gpio: gpiolib-cdev: Fix potential &lr->wait.lock deadlock issue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 26 Jun 2023 14:13:45 +0300
From:   "andy@...nel.org" <andy@...nel.org>
To:     YE Chengfeng <cyeaa@...nect.ust.hk>
Cc:     Kent Gibson <warthog618@...il.com>,
        "linus.walleij@...aro.org" <linus.walleij@...aro.org>,
        "brgl@...ev.pl" <brgl@...ev.pl>,
        "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] gpio: gpiolib-cdev: Fix potential &lr->wait.lock
 deadlock issue

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