All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: kernel-janitors@vger.kernel.org, Linux-NFS <linux-nfs@vger.kernel.org>
Subject: [nfs:nfs-for-bryan 100/100] net/sunrpc/auth_gss/gss_mech_switch.c:252:5: sparse: context imbalance i
Date: Tue, 17 Jul 2012 00:14:10 +0000	[thread overview]
Message-ID: <20120717001410.GD16944@localhost> (raw)

Hi Chuck,

There are new sparse warnings (likely a true locking bug) show up in

tree:   git://git.linux-nfs.org/projects/trondmy/linux-nfs.git nfs-for-bryan
head:   6a1a1e34dc55f17e7bd260809207442dbb7a0296
commit: 6a1a1e34dc55f17e7bd260809207442dbb7a0296 [100/100] SUNRPC: Add rpcauth_list_flavors()

All sparse warnings:

  net/sunrpc/auth_gss/gss_mech_switch.c:143:21: sparse: symbol '_gss_mech_get_by_name' was not declared. Should it be static?
  net/sunrpc/auth_gss/gss_mech_switch.c:208:21: sparse: symbol '_gss_mech_get_by_pseudoflavor' was not declared. Should it be static?
+ net/sunrpc/auth_gss/gss_mech_switch.c:252:5: sparse: context imbalance in 'gss_mech_list_pseudoflavors' - wrong count at exit

vim +252 net/sunrpc/auth_gss/gss_mech_switch.c
   249	 * The returned array is not sorted by any policy.  Callers should not
   250	 * rely on the order of the items in the returned array.
   251	 */
 > 252	int gss_mech_list_pseudoflavors(rpc_authflavor_t *array_ptr, int size)
   253	{
   254		struct gss_api_mech *pos = NULL;
   255		int j, i = 0;

---
0-DAY kernel build testing backend         Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com>                     Intel Corporation

WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: kernel-janitors@vger.kernel.org, Linux-NFS <linux-nfs@vger.kernel.org>
Subject: [nfs:nfs-for-bryan 100/100] net/sunrpc/auth_gss/gss_mech_switch.c:252:5: sparse: context imbalance in 'gss_mech_list_pseudoflavors' - wrong count at exit
Date: Tue, 17 Jul 2012 08:14:10 +0800	[thread overview]
Message-ID: <20120717001410.GD16944@localhost> (raw)

Hi Chuck,

There are new sparse warnings (likely a true locking bug) show up in

tree:   git://git.linux-nfs.org/projects/trondmy/linux-nfs.git nfs-for-bryan
head:   6a1a1e34dc55f17e7bd260809207442dbb7a0296
commit: 6a1a1e34dc55f17e7bd260809207442dbb7a0296 [100/100] SUNRPC: Add rpcauth_list_flavors()

All sparse warnings:

  net/sunrpc/auth_gss/gss_mech_switch.c:143:21: sparse: symbol '_gss_mech_get_by_name' was not declared. Should it be static?
  net/sunrpc/auth_gss/gss_mech_switch.c:208:21: sparse: symbol '_gss_mech_get_by_pseudoflavor' was not declared. Should it be static?
+ net/sunrpc/auth_gss/gss_mech_switch.c:252:5: sparse: context imbalance in 'gss_mech_list_pseudoflavors' - wrong count at exit

vim +252 net/sunrpc/auth_gss/gss_mech_switch.c
   249	 * The returned array is not sorted by any policy.  Callers should not
   250	 * rely on the order of the items in the returned array.
   251	 */
 > 252	int gss_mech_list_pseudoflavors(rpc_authflavor_t *array_ptr, int size)
   253	{
   254		struct gss_api_mech *pos = NULL;
   255		int j, i = 0;

---
0-DAY kernel build testing backend         Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com>                     Intel Corporation

             reply	other threads:[~2012-07-17  0:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17  0:14 Fengguang Wu [this message]
2012-07-17  0:14 ` [nfs:nfs-for-bryan 100/100] net/sunrpc/auth_gss/gss_mech_switch.c:252:5: sparse: context imbalance in 'gss_mech_list_pseudoflavors' - wrong count at exit Fengguang Wu
2012-07-17  0:52 ` [nfs:nfs-for-bryan 100/100] net/sunrpc/auth_gss/gss_mech_switch.c:252:5: sparse: context imbalan Chuck Lever
2012-07-17  0:52   ` [nfs:nfs-for-bryan 100/100] net/sunrpc/auth_gss/gss_mech_switch.c:252:5: sparse: context imbalance in 'gss_mech_list_pseudoflavors' - wrong count at exit Chuck Lever

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=20120717001410.GD16944@localhost \
    --to=fengguang.wu@intel.com \
    --cc=chuck.lever@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.