Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: Hemant Kumar <hemantk@codeaurora.org>,
	linux-arm-msm@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [bug report] bus: mhi: core: Add support for data transfer
Date: Fri, 17 Apr 2020 13:24:20 +0300	[thread overview]
Message-ID: <20200417102420.GR1163@kadam> (raw)
In-Reply-To: <20200417101428.GA10295@Mani-XPS-13-9360>

On Fri, Apr 17, 2020 at 03:44:28PM +0530, Manivannan Sadhasivam wrote:
> Hi Hemant,
> 
> On Thu, Apr 16, 2020 at 08:37:16PM -0700, Hemant Kumar wrote:
> > 
> > On 4/7/20 7:33 AM, Manivannan Sadhasivam wrote:
> > > Hi Dan,
> > > 
> > > On Tue, Apr 07, 2020 at 04:55:59PM +0300, Dan Carpenter wrote:
> > > > Hello Manivannan Sadhasivam,
> > > > 
> > > > The patch 189ff97cca53: "bus: mhi: core: Add support for data
> > > > transfer" from Feb 20, 2020, leads to the following static checker
> > > > warning:
> > > > 
> > > > 	drivers/bus/mhi/core/main.c:1153 mhi_queue_buf()
> > > > 	error: double locked 'mhi_chan->lock' (orig line 1110)
> > > > 
> > > > drivers/bus/mhi/core/main.c
> > > >    1142          }
> > > >    1143
> > > >    1144          /* Toggle wake to exit out of M2 */
> > > >    1145          mhi_cntrl->wake_toggle(mhi_cntrl);
> > > >    1146
> > > >    1147          if (mhi_chan->dir == DMA_TO_DEVICE)
> > > >    1148                  atomic_inc(&mhi_cntrl->pending_pkts);
> > > >    1149
> > > >    1150          if (likely(MHI_DB_ACCESS_VALID(mhi_cntrl))) {
> > > >    1151                  unsigned long flags;
> > > >    1152
> > > >    1153                  read_lock_irqsave(&mhi_chan->lock, flags);
> > 
> > parse_xfer_event is taking read lock : read_lock_bh(&mhi_chan->lock); first
> > and later
> > 
> > mhi_queue_buf takes read lock: read_lock_irqsave(&mhi_chan->lock, flags);
> > 
> > Both are read locks which are recursive, is this problematic ?
> > 
> 
> read_locks are recursive but I wanted to make the static checker happy.

Don't do things just to make the static checker happy.

regards,
dan carpenter


  reply	other threads:[~2020-04-17 10:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07 13:55 [bug report] bus: mhi: core: Add support for data transfer Dan Carpenter
2020-04-07 14:33 ` Manivannan Sadhasivam
2020-04-17  3:37   ` Hemant Kumar
2020-04-17 10:14     ` Manivannan Sadhasivam
2020-04-17 10:24       ` Dan Carpenter [this message]
2020-04-18  7:10       ` Hemant Kumar
2020-04-18 19:19         ` Manivannan Sadhasivam
2020-04-20 22:57           ` Hemant Kumar
2020-04-21  5:52             ` Manivannan Sadhasivam
2020-04-21  6:03 ` Manivannan Sadhasivam
  -- strict thread matches above, loose matches on Subject: below --
2020-04-07 13:56 Dan Carpenter
2020-04-07 14:31 ` Manivannan Sadhasivam

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=20200417102420.GR1163@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=hemantk@codeaurora.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    /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