From: Julia Lawall <julia.lawall@lip6.fr>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: kbuild test robot <lkp@intel.com>,
Shivani Bhardwaj <shivanib134@gmail.com>,
kbuild-all@01.org, andreas.dilger@intel.com,
oleg.drokin@intel.com, lustre-devel@lists.lustre.org,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH] staging: lustre: acl: fix ifnullfree.cocci warnings
Date: Mon, 9 Nov 2015 22:04:40 +0000 (GMT) [thread overview]
Message-ID: <alpine.DEB.2.10.1511092157470.3844@hadrien> (raw)
In-Reply-To: <20151109195902.GB11820@kroah.com>
On Mon, 9 Nov 2015, Greg KH wrote:
> On Tue, Nov 10, 2015 at 03:43:50AM +0800, kbuild test robot wrote:
> > 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);
>
> Looks like a bug in coccinelle, the comment line should also be indented
> to the left.
>
> Julia, any ideas?
I think it's on the border of what the person is going to have to resign
themselves to doing by hand. I'm not sure which side of the border it is
on, but I try to focus more on getting the code printed in the right place
than on the comments. I can check on it, though, and maybe an easy fix is
possible.
thanks,
julia
prev parent reply other threads:[~2015-11-09 22:04 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 ` [PATCH] staging: lustre: acl: fix ifnullfree.cocci warnings kbuild test robot
2015-11-09 19:59 ` Greg KH
2015-11-09 22:04 ` Julia Lawall [this message]
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=alpine.DEB.2.10.1511092157470.3844@hadrien \
--to=julia.lawall@lip6.fr \
--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=lkp@intel.com \
--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®