From: kbuild test robot <lkp@intel.com>
To: Shivani Bhardwaj <shivanib134@gmail.com>
Cc: kbuild-all@01.org, gregkh@linuxfoundation.org,
andreas.dilger@intel.com, oleg.drokin@intel.com,
lustre-devel@lists.lustre.org, linux-kernel@vger.kernel.org,
devel@driverdev.osuosl.org
Subject: [PATCH] staging: lustre: acl: fix ifnullfree.cocci warnings
Date: Tue, 10 Nov 2015 03:43:50 +0800 [thread overview]
Message-ID: <20151109194350.GA117144@cairo> (raw)
In-Reply-To: <1447095257-21165-1-git-send-email-shivanib134@gmail.com>
drivers/staging/lustre/lustre/llite/xattr.c:199:2-7: WARNING: NULL check before freeing functions like kfree, debugfs_remove, debugfs_remove_recursive or usb_free_urb is not needed. Maybe consider reorganizing relevant code to avoid passing NULL values.
NULL check before some freeing functions is not needed.
Based on checkpatch warning
"kfree(NULL) is safe this check is probably not required"
and kfreeaddr.cocci by Julia Lawall.
Generated by: scripts/coccinelle/free/ifnullfree.cocci
CC: Shivani Bhardwaj <shivanib134@gmail.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
xattr.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--- a/drivers/staging/lustre/lustre/llite/xattr.c
+++ b/drivers/staging/lustre/lustre/llite/xattr.c
@@ -192,11 +192,10 @@ int ll_setxattr_common(struct inode *ino
valid, name, pv, size, 0, flags,
ll_i2suppgid(inode), &req);
#ifdef CONFIG_FS_POSIX_ACL
- if (new_value != NULL)
/*
* Release the posix ACL space.
*/
- kfree(new_value);
+ kfree(new_value);
if (acl != NULL)
lustre_ext_acl_xattr_free(acl);
#endif
next prev parent reply other threads:[~2015-11-09 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 19:43 [PATCH] staging: lustre: acl: Remove lustre_posix_acl_xattr_free wrapper kbuild test robot
2015-11-09 18:54 ` Shivani Bhardwaj
2015-11-09 19:43 ` kbuild test robot [this message]
2015-11-09 19:59 ` [PATCH] staging: lustre: acl: fix ifnullfree.cocci warnings Greg KH
2015-11-09 22:04 ` Julia Lawall
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=20151109194350.GA117144@cairo \
--to=lkp@intel.com \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.com \
--cc=shivanib134@gmail.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
all inboxes | Powered by JetHome®