From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [dlm:next 1/6] fs/dlm/lock.c:1049:9: sparse: context imbalance in 'dlm_master_lookup' - different lo
Date: Tue, 17 Jul 2012 00:10:14 +0000 [thread overview]
Message-ID: <20120717001014.GC16944@localhost> (raw)
Hi David,
I don't know enough to tell whether this if false alarm. Would you
help confirm it? Thank you.
tree: git://git.kernel.org/pub/scm/linux/kernel/git/teigland/linux-dlm.git next
head: 96006ea6d4eea73466e90ef353bf34e507724e77
commit: c04fecb4d9f7753e0cbff7edd03ec68f8721cdce [1/6] dlm: use rsbtbl as resource directory
One new sparse warning is triggered (and there were no old warnings before patch):
+ fs/dlm/lock.c:1049:9: sparse: context imbalance in 'dlm_master_lookup' - different lock contexts for basic block
vim +1049 fs/dlm/lock.c
1046 unlock_rsb(r);
1047 put_rsb(r);
1048 }
> 1049 return 0;
1050
1051 not_found:
1052 error = get_rsb_struct(ls, name, len, &r);
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com> Intel Corporation
next reply other threads:[~2012-07-17 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 0:10 Fengguang Wu [this message]
2012-07-17 14:35 ` [dlm:next 1/6] fs/dlm/lock.c:1049:9: sparse: context imbalance in 'dlm_master_lookup' - differen David Teigland
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=20120717001014.GC16944@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@vger.kernel.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