From: Greg KH <gregkh@linuxfoundation.org>
To: Nayeemahmed Badebade <itachi.opsrc@gmail.com>
Cc: oleg.drokin@intel.com, andreas.dilger@intel.com,
jsimmons@infradead.org, Keith.Mannthey@intel.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
bruce.korb@gmail.com, lustre-devel@lists.lustre.org
Subject: Re: [PATCH] staging: lustre: lustre/ldlm: Fixed sparse warnings
Date: Mon, 12 Sep 2016 12:27:47 +0200 [thread overview]
Message-ID: <20160912102747.GA13621@kroah.com> (raw)
In-Reply-To: <1473434435-27025-1-git-send-email-itachi.opsrc@gmail.com>
On Fri, Sep 09, 2016 at 08:50:35PM +0530, Nayeemahmed Badebade wrote:
> Added __acquires / __releases sparse locking annotations
> to lock_res_and_lock and unlock_res_and_lock functions in
> l_lock.c, to fix below sparse warnings:
>
> l_lock.c:47:22: warning: context imbalance in 'lock_res_and_lock' - wrong count at exit
> l_lock.c:62:6: warning: context imbalance in 'unlock_res_and_lock' - unexpected unlock
>
> Signed-off-by: Nayeemahmed Badebade <itachi.opsrc@gmail.com>
> ---
> drivers/staging/lustre/lustre/ldlm/l_lock.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/staging/lustre/lustre/ldlm/l_lock.c b/drivers/staging/lustre/lustre/ldlm/l_lock.c
> index ea8840c..c4b9612 100644
> --- a/drivers/staging/lustre/lustre/ldlm/l_lock.c
> +++ b/drivers/staging/lustre/lustre/ldlm/l_lock.c
> @@ -45,6 +45,8 @@
> * being an atomic operation.
> */
> struct ldlm_resource *lock_res_and_lock(struct ldlm_lock *lock)
> + __acquires(&lock->l_lock)
> + __acquires(lock->l_resource)
Hm, these are tricky, I don't want to take this type of change without
an ack from the lustre developers...
thanks,
greg k-h
next prev parent reply other threads:[~2016-09-12 10:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 15:20 Nayeemahmed Badebade
2016-09-12 10:27 ` Greg KH [this message]
2016-09-14 5:14 ` Dilger, Andreas
2016-09-15 18:33 ` nayeem
2016-09-16 8:00 ` Dilger, Andreas
2016-09-18 20:21 ` nayeem
2016-09-18 20:29 ` Dilger, Andreas
2016-09-18 21:18 ` [PATCH v2] " Nayeemahmed Badebade
2016-09-18 21:27 ` Dilger, Andreas
2016-09-19 20:43 ` James Simmons
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=20160912102747.GA13621@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Keith.Mannthey@intel.com \
--cc=andreas.dilger@intel.com \
--cc=bruce.korb@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=itachi.opsrc@gmail.com \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.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
Powered by JetHome