From: David Miller <davem@davemloft.net>
To: ecree@solarflare.com
Cc: linux-net-drivers@solarflare.com, netdev@vger.kernel.org,
linux@roeck-us.net
Subject: Re: [PATCH net] sfc: fix ef100 design-param checking
Date: Wed, 12 Aug 2020 13:06:06 -0700 (PDT) [thread overview]
Message-ID: <20200812.130606.1336382904304655382.davem@davemloft.net> (raw)
In-Reply-To: <311d8274-9c6f-4614-552f-b1d3da64f368@solarflare.com>
From: Edward Cree <ecree@solarflare.com>
Date: Wed, 12 Aug 2020 10:32:49 +0100
> The handling of the RXQ/TXQ size granularity design-params had two
> problems: it had a 64-bit divide that didn't build on 32-bit platforms,
> and it could divide by zero if the NIC supplied 0 as the value of the
> design-param. Fix both by checking for 0 and for a granularity bigger
> than our min-size; if the granularity <= EFX_MIN_DMAQ_SIZE then it fits
> in 32 bits, so we can cast it to u32 for the divide.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Edward Cree <ecree@solarflare.com>
Applied.
prev parent reply other threads:[~2020-08-12 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 9:32 [PATCH net] sfc: fix ef100 design-param checking Edward Cree
2020-08-12 15:23 ` Guenter Roeck
2020-08-12 20:06 ` David Miller [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=20200812.130606.1336382904304655382.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=linux-net-drivers@solarflare.com \
--cc=linux@roeck-us.net \
--cc=netdev@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 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).