[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <60931201-FD2A-4579-861E-E9573B7C2B38@connect.ust.hk>
Date: Mon, 26 Jun 2023 17:05:38 +0000
From: YE Chengfeng <cyeaa@...nect.ust.hk>
To: Ray Jui <ray.jui@...adcom.com>
CC: "andi.shyti@...nel.org" <andi.shyti@...nel.org>,
"rjui@...adcom.com" <rjui@...adcom.com>,
"sbranden@...adcom.com" <sbranden@...adcom.com>,
"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"bcm-kernel-feedback-list@...adcom.com"
<bcm-kernel-feedback-list@...adcom.com>
Subject: Re: [PATCH] i2c: bcm-iproc: Fix bcm_iproc_i2c_isr deadlock issue
> This fix looks good to me. Thanks. Just curious, did you actually see a
> race condition issue as a result of this, or the fix is done completely
> based on the analysis of the code?
Thanks for the reply!
This bug is detected by a static analysis tool built by me, I just notice I should
mention this in the commit message and sorry for not have made it clear. I noticed
lockdep occasionally reported such similar deadlocks in other place thus built the
static tool to locate such bugs.
Just feel free to let me know if anything in the patch should be improved.
Best Regards,
Chengfeng
Powered by blists - more mailing lists