All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sesterhenn / Snakebyte <snakebyte@gmx.de>
To: Russ Cox <rsc@swtch.com>
Cc: Eric Sesterhenn <snakebyte@gmx.de>,
	linux-kernel@vger.kernel.org,
	v9fs-developer@lists.sourceforge.net
Subject: Re: [V9fs-developer] [Patch] Dead code in fs/9p/vfs_inode.c
Date: Thu, 29 Jun 2006 01:16:28 +0200	[thread overview]
Message-ID: <20060628231627.GA28463@alice> (raw)
In-Reply-To: <ee9e417a0606281555k3d954236y82b11336098762be@mail.gmail.com>

* Russ Cox (rsc@swtch.com) wrote:
> >coverity (id #971) found some dead code. In all error
> >cases ret is NULL, so we can remove the if statement.
> >
> >Signed-off-by: Eric Sesterhenn <snakebyte@gmx.de>
> >
> >--- linux-2.6.17-git11/fs/9p/vfs_inode.c.orig   2006-06-29 
> >00:50:53.000000000 +0200
> >+++ linux-2.6.17-git11/fs/9p/vfs_inode.c        2006-06-29 
> >00:51:11.000000000 +0200
> >@@ -386,9 +386,6 @@ v9fs_inode_from_fid(struct v9fs_session_
> >
> > error:
> >        kfree(fcall);
> >-       if (ret)
> >-               iput(ret);
> >-
> >        return ERR_PTR(err);
> > }
> 
> What about when someone changes the code and does have ret != NULL here?
> This seems like reasonable defensive programming to me.
> 
> Is the official LK policy that we can't have code that trips coverity
> checks like this?

If this is whats agreed upon I will no longer send patches for
such bugs, and mark them as ignore in the coverity system.
But I guess it makes also sense to remove unused code, because I
am not sure if gcc can figure out to remove it. In this case
the generated object file is 10 bytes smaller.

Eric


  reply	other threads:[~2006-06-28 23:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 22:52 [Patch] Dead code in fs/9p/vfs_inode.c Eric Sesterhenn
2006-06-28 22:55 ` [V9fs-developer] " Russ Cox
2006-06-28 23:16   ` Eric Sesterhenn / Snakebyte [this message]
2006-06-28 23:24     ` Russ Cox
2006-06-28 23:41       ` Eric Sesterhenn / Snakebyte
2006-06-29  3:58     ` David Leimbach
2006-06-29  5:27   ` Pekka Enberg
2006-06-29 11:01   ` Jan Engelhardt
2006-06-29 15:16     ` Latchesar Ionkov
2006-06-30 13:44       ` Jan Engelhardt
2006-06-30 14:12         ` erik quanstrom

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=20060628231627.GA28463@alice \
    --to=snakebyte@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rsc@swtch.com \
    --cc=v9fs-developer@lists.sourceforge.net \
    /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.