[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VeuumsZHDdue=n-2esyG7Q-6472JoYJ64U0+OQoC2psgQ@mail.gmail.com>
Date: Sat, 3 Jun 2017 18:55:57 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Colin King <colin.king@...onical.com>
Cc: Giuseppe Cavallaro <peppe.cavallaro@...com>,
Alexandre Torgue <alexandre.torgue@...com>,
netdev <netdev@...r.kernel.org>, kernel-janitors@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] net: stmmac: ensure jumbo_frm error return is correctly
checked for -ve value
On Fri, Jun 2, 2017 at 5:58 PM, Colin King <colin.king@...onical.com> wrote:
> The current comparison of entry < 0 will never be true since entry is an
> unsigned integer. Cast entry to an int to ensure -ve error return values
> from the call to jumbo_frm are correctly being caught.
> if (unlikely(is_jumbo) && likely(priv->synopsys_id <
> DWMAC_CORE_4_00)) {
> entry = priv->hw->mode->jumbo_frm(tx_q, skb, csum_insertion);
> - if (unlikely(entry < 0))
> + if (unlikely((int)entry < 0))
It feels like a hiding some other issue.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists