From: Andrew Morton <akpm@osdl.org>
To: Christoph Hellwig <hch@lst.de>
Cc: zkambarov@coverity.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix Coverity braindamage in UDF
Date: Wed, 29 Jun 2005 00:13:17 -0700 [thread overview]
Message-ID: <20050629001317.019476d9.akpm@osdl.org> (raw)
In-Reply-To: <20050629070309.GA18901@lst.de>
Christoph Hellwig <hch@lst.de> wrote:
>
> Andrew, please don't blindly apply Coverity patches. While the checker
> is smart at finding inconsistencies, that "obvious" fix is wrong most of
> the item. As in this unreviewed UDF patch that got in:
> udf_find_entry can never be called with a NULL argument, so we shouldn't
> check for it instead of adding more assignments behind the check.
I reviewed it. The code as it stood was wrong and the patch corrected it.
Yes, I realised at the time that the test for null is probably redundant,
but that's a separate thing - we have many such redundant tests and perhaps
someone should do a cleanup sweep. But I have no intention of doing that
and I don't want to be leaving obvious coding errors in there.
A similar argument applies to the patch "coverity: tty_ldisc_ref return
null check".
prev parent reply other threads:[~2005-06-29 7:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 7:03 Christoph Hellwig
2005-06-29 7:13 ` Andrew Morton [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=20050629001317.019476d9.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zkambarov@coverity.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®