From: Jakub Kicinski <kuba@kernel.org>
To: Martin Habets <habetsm.xilinx@gmail.com>
Cc: davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
netdev@vger.kernel.org, ecree.xilinx@gmail.com,
linux-net-drivers@amd.com
Subject: Re: [PATCH net] sfc: support for devlink port requires MAE access
Date: Thu, 29 Jun 2023 11:11:42 -0700 [thread overview]
Message-ID: <20230629111142.133d3610@kernel.org> (raw)
In-Reply-To: <168795553996.2797.7851805610285857967.stgit@palantir17.mph.net>
On Wed, 28 Jun 2023 13:32:20 +0100 Martin Habets wrote:
> On systems without MAE permission efx->mae is not initialised,
> and trying to lookup an mport results in a NULL pointer
> dereference.
>
> Fixes: 25414b2a64ae ("sfc: add devlink port support for ef100")
> Signed-off-by: Martin Habets <habetsm.xilinx@gmail.com>
Applied (manually) thanks!
parent reply other threads:[~2023-06-29 18:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <168795553996.2797.7851805610285857967.stgit@palantir17.mph.net>]
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=20230629111142.133d3610@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=habetsm.xilinx@gmail.com \
--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).