From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: Edward Cree <ecree.xilinx@gmail.com>
Cc: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
edward.cree@amd.com, linux-net-drivers@amd.com,
davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, andrew+netdev@lunn.ch,
netdev@vger.kernel.org, Kyungwook Boo <bookyungwook@gmail.com>
Subject: Re: [PATCH net] sfc: fix NULL dereferences in ef100_process_design_param()
Date: Wed, 2 Apr 2025 11:50:12 +0200 [thread overview]
Message-ID: <Z+0ITvrUaZSfdehU@mev-dev.igk.intel.com> (raw)
In-Reply-To: <98a26384-5d6f-d5d2-3ecc-1914a74299eb@gmail.com>
On Wed, Apr 02, 2025 at 09:15:02AM +0100, Edward Cree wrote:
> On 02/04/2025 06:17, Michal Swiatkowski wrote:
> > On Tue, Apr 01, 2025 at 11:54:39PM +0100, edward.cree@amd.com wrote:
> >> - netif_set_tso_max_segs(net_dev,
> >> - ESE_EF100_DP_GZ_TSO_MAX_HDR_NUM_SEGS_DEFAULT);
> >> + nic_data = efx->nic_data;
> >> + netif_set_tso_max_size(efx->net_dev, nic_data->tso_max_payload_len);
> >> + netif_set_tso_max_segs(efx->net_dev, nic_data->tso_max_payload_num_segs);
> >
> > Is it fine to drop default value for max segs? Previously if somehow
> > this value wasn't read from HW it was set to default, now it will be 0.
> >
> > At the beggining of ef100_probe_main() default values for nic_data are
> > set. Maybe it is worth to set also this default for max segs?
>
> As I read it, ef100_probe_main() does set a default for this nic_data
> field along with the others, and sets it to exactly this same value.
>
Sorry, right, I somehow missed it.
Reviewed-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> confused,
> -ed
next prev parent reply other threads:[~2025-04-02 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 22:54 [PATCH net] sfc: fix NULL dereferences in ef100_process_design_param() edward.cree
2025-04-02 5:17 ` Michal Swiatkowski
2025-04-02 8:15 ` Edward Cree
2025-04-02 9:50 ` Michal Swiatkowski [this message]
2025-04-03 22:20 ` patchwork-bot+netdevbpf
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=Z+0ITvrUaZSfdehU@mev-dev.igk.intel.com \
--to=michal.swiatkowski@linux.intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=bookyungwook@gmail.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=edward.cree@amd.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).