From: Eric Sesterhenn / Snakebyte <snakebyte@gmx.de>
To: Russ Cox <rsc@swtch.com>
Cc: Eric Sesterhenn / Snakebyte <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:41:02 +0200 [thread overview]
Message-ID: <20060628234102.GB28463@alice> (raw)
In-Reply-To: <ee9e417a0606281624t23f5ccc2qd095b9bf993a0861@mail.gmail.com>
* Russ Cox (rsc@swtch.com) wrote:
> >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.
>
> I wasn't necessarily speaking for the group so much as I was interested
> in how coverity was being used and what the rules were.
> Thanks for the info.
guess thats depends on the person looking trough the bugs :)
As far as i know, there are no official rules ( except maybe
to never let gregkh see a false positive :), i just try to
take a look at the coverity reports, and fix whatever I can,
in cleanup cases like this it clearly depends on the maintainer,
what he does with the patch. the coverity guys seem to be pretty
nice in giving accounts away, so you might want to take a look
at this stuff yourself. At the moment about half of the inspected
"bugs" have been marked as invalid or false, to shut coverity up
about clearly defensive programming or false analysis, so i guess
the main part is not to make coverity shut up with a patch, since
marking it as invalid is much less hassle.
Eric
next prev parent reply other threads:[~2006-06-28 23:41 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
2006-06-28 23:24 ` Russ Cox
2006-06-28 23:41 ` Eric Sesterhenn / Snakebyte [this message]
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=20060628234102.GB28463@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox