All of lore.kernel.org
 help / color / mirror / Atom feed
* e2fsprogs coverity patch <cid-2.diff>
@ 2007-02-10  2:11 Brian D. Behlendorf
  2007-03-18 14:04 ` e2fsprogs coverity patch <cid-02.diff> Theodore Tso
  0 siblings, 1 reply; 2+ messages in thread
From: Brian D. Behlendorf @ 2007-02-10  2:11 UTC (permalink / raw)
  To: tytso; +Cc: linux-ext4, adilger, behlendorf1, wartens2

Lawrence Livermore National Labs recently ran the source code
analysis tool Coverity over the e2fsprogs-1.39 source to see 
if it would identify any significant bugs.  The analysis
turned up 38 mostly minor issues which are enumerated here
with patches.  We went through and resolved these issues
but would love to see these mostly minor changes reviewed
and commited upstream.

Thanks,
Brian Behlendorf <behlendorf1@llnl.gov>, and
Herb Wartens <wartens2@llnl.gov>

-----------------------------------------------------------------------------
Coverity ID: 2: Deadcode

Looks like ss_current_request is a macro that will set code to 0. This test
will always be false. I will remove this error case.

Index: e2fsprogs+chaos/lib/ss/help.c
===================================================================
--- e2fsprogs+chaos.orig/lib/ss/help.c
+++ e2fsprogs+chaos/lib/ss/help.c
@@ -49,10 +49,6 @@ void ss_help (argc, argv, sci_idx, info_
     register ss_data *info;
 
     request_name = ss_current_request(sci_idx, &code);
-    if (code != 0) {
-	ss_perror(sci_idx, code, "");
-	return;		/* no ss_abort_line, if invalid invocation */
-    }
     if (argc == 1) {
 	ss_list_requests(argc, argv, sci_idx, info_ptr);
 	return;

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: e2fsprogs coverity patch <cid-02.diff>
  2007-02-10  2:11 e2fsprogs coverity patch <cid-2.diff> Brian D. Behlendorf
@ 2007-03-18 14:04 ` Theodore Tso
  0 siblings, 0 replies; 2+ messages in thread
From: Theodore Tso @ 2007-03-18 14:04 UTC (permalink / raw)
  To: Brian D. Behlendorf; +Cc: linux-ext4, adilger, wartens2

On Fri, Feb 09, 2007 at 06:11:17PM -0800, Brian D. Behlendorf wrote:
> Looks like ss_current_request is a macro that will set code to 0. This test
> will always be false. I will remove this error case.

The ss library is pretty stable, yes, but it's a bad idea to remove an
error check which is mandated by the interface defintion; what if the
implementation changes in the future?

Probably the better way to shut up coverity in this case is to replace
the current implementation of ss_current_request with a C version
which checks to make sure sci_idx is valid (as opposed to blindly
indexing off the array and potentially causing a seg fault), and
returning EINVAL if sci_idx is invalid.

I will NOT do this fixup now, but I will queue it in a future
(low-priority) TODO list.  Fixes to do this are welcome.

					- Ted

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-03-18 14:04 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-02-10  2:11 e2fsprogs coverity patch <cid-2.diff> Brian D. Behlendorf
2007-03-18 14:04 ` e2fsprogs coverity patch <cid-02.diff> Theodore Tso

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.