From: Nguyen, Anthony L <anthony.l.nguyen@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net v1] i40e: Fix NULL pointer dereference in i40e_dbg_dump_desc
Date: Fri, 19 Nov 2021 18:22:30 +0000 [thread overview]
Message-ID: <491af7df6c21a21148316723ab4b720e7bbdcd90.camel@intel.com> (raw)
In-Reply-To: <20211117101737.8961-1-mateusz.palczewski@intel.com>
On Wed, 2021-11-17 at 11:17 +0100, Mateusz Palczewski wrote:
> From: Norbert Zulinski <norbertx.zulinski@intel.com>
>
> When trying to dump VFs VSI RX/TX descriptors
> using debugfs there was a crash
> due to NULL pointer dereference in i40e_dbg_dump_desc.
> Added a check to i40e_dbg_dump_desc that checks if
> VSI type is correct for dumping RX/TX descriptors.
>
> Fixes: 02e9c290814c ("i40e: debugfs interface")
> Signed-off-by: Sylwester Dziedziuch <sylwesterx.dziedziuch@intel.com>
> Signed-off-by: Mateusz Palczewski <mateusz.palczewski@intel.com>
There is no Signed-off-by from the author.
prev parent reply other threads:[~2021-11-19 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 10:17 [Intel-wired-lan] [PATCH net v1] i40e: Fix NULL pointer dereference in i40e_dbg_dump_desc Mateusz Palczewski
2021-11-19 18:22 ` Nguyen, Anthony L [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=491af7df6c21a21148316723ab4b720e7bbdcd90.camel@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@osuosl.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