Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: naamax.meir <naamax.meir@linux.intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v2 1/1] e1000e: Fix possible overflow in LTR decoding
Date: Wed, 6 Apr 2022 08:05:45 +0300	[thread overview]
Message-ID: <c5a1da34-0c31-32ea-17c5-9c51159ffbee@linux.intel.com> (raw)
In-Reply-To: <20220405155601.1443799-1-sasha.neftin@intel.com>

On 4/5/2022 18:56, Sasha Neftin wrote:
> When we decode the latency and the max_latency u16 value does not fill
> the required size and could lead to the wrong LTR representation.
> Replace the u16 type with the u32 type and allow corrected LTR
> representation.
> 
> Fixes: 44a13a5d99c7 ("e1000e: Fix the max snoop/no-snoop latency for 10M")
> Reported-by: James Hutchinson <jahutchinson99@googlemail.com>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=215689
> Suggested-by: Dima Ruinskiy <dima.ruinskiy@intel.com>
> Signed-off-by: Sasha Neftin <sasha.neftin@intel.com>
> ---
> v2: added link tag
> 
>   drivers/net/ethernet/intel/e1000e/ich8lan.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
Tested-by: Naama Meir <naamax.meir@linux.intel.com>

  reply	other threads:[~2022-04-06  5:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 15:56 [Intel-wired-lan] [PATCH v2 1/1] e1000e: Fix possible overflow in LTR decoding Sasha Neftin
2022-04-06  5:05 ` naamax.meir [this message]
2022-04-06  5:34 ` Paul Menzel
2022-04-06 14:33   ` Neftin, Sasha
2022-04-06 15:22     ` James Hutchinson
2022-04-10 10:10     ` Paul Menzel
2022-04-11 22:21       ` Tony Nguyen

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=c5a1da34-0c31-32ea-17c5-9c51159ffbee@linux.intel.com \
    --to=naamax.meir@linux.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