All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next PATCH] i40e: Fix of memory leak and integer truncation in i40e_virtchnl.c
Date: Fri, 19 Apr 2019 17:17:17 +0000	[thread overview]
Message-ID: <26D9FDECA4FBDD4AADA65D8E2FC68A4A1D38EE59@ORSMSX104.amr.corp.intel.com> (raw)
In-Reply-To: <20190416221546.22721-1-alice.michael@intel.com>

> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On
> Behalf Of Alice Michael
> Sent: Tuesday, April 16, 2019 3:16 PM
> To: Michael, Alice <alice.michael@intel.com>; intel-wired-
> lan at lists.osuosl.org
> Cc: Szapar, Martyna <martyna.szapar@intel.com>
> Subject: [Intel-wired-lan] [next PATCH] i40e: Fix of memory leak and integer
> truncation in i40e_virtchnl.c
> 
> From: Martyna Szapar <martyna.szapar@intel.com>
> 
> Fixed possible memory leak in i40e_vc_add_cloud_filter function:
> cfilter is being allocated and in some error conditions the function returns
> without freeing the memory.
> 
> Fix of integer truncation from u16 (type of queue_id value) to u8 when
> calling i40e_vc_isvalid_queue_id function.
> 
> Signed-off-by: Martyna Szapar <martyna.szapar@intel.com>
> ---
>  .../net/ethernet/intel/i40e/i40e_virtchnl_pf.c   | 16 ++++++++++------
>  1 file changed, 10 insertions(+), 6 deletions(-)

Tested-by: Andrew Bowers <andrewx.bowers@intel.com>



  reply	other threads:[~2019-04-19 17:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 22:15 [Intel-wired-lan] [next PATCH] i40e: Fix of memory leak and integer truncation in i40e_virtchnl.c Alice Michael
2019-04-19 17:17 ` Bowers, AndrewX [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-04-15 21:43 Alice Michael

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=26D9FDECA4FBDD4AADA65D8E2FC68A4A1D38EE59@ORSMSX104.amr.corp.intel.com \
    --to=andrewx.bowers@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.