From: Arnd Bergmann <arnd@arndb.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] dsp56k: prevent a harmless underflow
Date: Wed, 13 Jul 2016 15:01:35 +0000 [thread overview]
Message-ID: <4560698.1o7vFVpiPH@wuerfel> (raw)
In-Reply-To: <20160713101119.GF29468@mwanda>
On Wednesday, July 13, 2016 1:11:19 PM CEST Dan Carpenter wrote:
> There is a mistake here where we don't allow "len" to be zero but we
> allow negative lengths. It's basically harmless in this case, but the
> underflow makes my static checker complain.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] dsp56k: prevent a harmless underflow
Date: Wed, 13 Jul 2016 17:01:35 +0200 [thread overview]
Message-ID: <4560698.1o7vFVpiPH@wuerfel> (raw)
In-Reply-To: <20160713101119.GF29468@mwanda>
On Wednesday, July 13, 2016 1:11:19 PM CEST Dan Carpenter wrote:
> There is a mistake here where we don't allow "len" to be zero but we
> allow negative lengths. It's basically harmless in this case, but the
> underflow makes my static checker complain.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2016-07-13 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 10:11 [patch] dsp56k: prevent a harmless underflow Dan Carpenter
2016-07-13 10:11 ` Dan Carpenter
2016-07-13 15:01 ` Arnd Bergmann [this message]
2016-07-13 15:01 ` Arnd Bergmann
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=4560698.1o7vFVpiPH@wuerfel \
--to=arnd@arndb.de \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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.