From: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: "Gustavo A. R. Silva"
<garsilva-L1vi/lXTdts+Va1GwOuvDg@public.gmane.org>,
Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] iommu: remove unnecessary code
Date: Thu, 11 May 2017 09:01:44 +0100 [thread overview]
Message-ID: <1494489704.7803.28.camel@infradead.org> (raw)
In-Reply-To: <20170511034931.GA9483@embeddedgus>
[-- Attachment #1.1: Type: text/plain, Size: 1494 bytes --]
On Wed, 2017-05-10 at 22:49 -0500, Gustavo A. R. Silva wrote:
> did_old is an unsigned variable and, greater-than-or-equal-to-zero
> comparison of an unsigned variable is always true.
>
> Addresses-Coverity-ID: 1398477
> Signed-off-by: Gustavo A. R. Silva <garsilva-L1vi/lXTdts+Va1GwOuvDg@public.gmane.org>
So... why do you think that check was there? Do you think it's possible
that someone mistakenly *thought* it could be negative? What were they
actually checking for? Have you actually *fixed* a bug here, or have
you just masked it?
Even if you've done all that analysis and it *is* correct just to drop
the comparison rather than fixing it, you need to put verbiage to that
effect into the commit comment.
Never write patches to "fix warnings". Always to fix bugs.
> ---
> drivers/iommu/intel-iommu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c
> index d412a31..98daf4a 100644
> --- a/drivers/iommu/intel-iommu.c
> +++ b/drivers/iommu/intel-iommu.c
> @@ -2050,7 +2050,7 @@ static int domain_context_mapping_one(struct dmar_domain *domain,
> if (context_copied(context)) {
> u16 did_old = context_domain_id(context);
>
> - if (did_old >= 0 && did_old < cap_ndoms(iommu->cap))
> + if (did_old < cap_ndoms(iommu->cap))
> iommu->flush.flush_context(iommu, did_old,
> (((u16)bus) << 8) | devfn,
> DMA_CCMD_MASK_NOBIT,
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4938 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2017-05-11 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 3:49 [PATCH] iommu: remove unnecessary code Gustavo A. R. Silva
2017-05-11 8:01 ` David Woodhouse [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=1494489704.7803.28.camel@infradead.org \
--to=dwmw2-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=garsilva-L1vi/lXTdts+Va1GwOuvDg@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).