public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Maciej Rabeda" <maciej.rabeda@linux.intel.com>
To: devel@edk2.groups.io, jiaxin.wu@intel.com
Subject: Re: [edk2-devel] [PATCH v2] NetworkPkg/Ip6Dxe: Fix ASSERT logic in Ip6ProcessRouterAdvertise()
Date: Fri, 3 Apr 2020 14:36:04 +0200	[thread overview]
Message-ID: <22b2f78d-45bb-7b8b-c03d-17e0686478cb@linux.intel.com> (raw)
In-Reply-To: <895558F6EA4E3B41AC93A00D163B727417061717@SHSMSX107.ccr.corp.intel.com>

Hey Jiaxin!

Thanks for the review, I have already merged this patch based on 
Siyuan's review and Laszlo's test :)
Also, big thank you for handling the HTTP static IP thread.

- Maciej

On 03-Apr-20 09:21, Wu, Jiaxin wrote:
> Reviewed-by: Jiaxin Wu <jiaxin.wu@intel.com>
>
>
>> -----Original Message-----
>> From: Maciej Rabeda <maciej.rabeda@linux.intel.com>
>> Sent: Thursday, April 2, 2020 5:15 PM
>> To: devel@edk2.groups.io
>> Cc: Wu, Jiaxin <jiaxin.wu@intel.com>; Fu, Siyuan <siyuan.fu@intel.com>;
>> Laszlo Ersek <lersek@redhat.com>
>> Subject: [PATCH v2] NetworkPkg/Ip6Dxe: Fix ASSERT logic in
>> Ip6ProcessRouterAdvertise()
>>
>> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2655
>>
>> This patch fixes reversed logic of recently added ASSERTs which should
>> ensure that Ip6IsNDOptionValid() implementation properly reacts to invalid
>> packets.
>>
>> Cc: Jiaxin Wu <jiaxin.wu@intel.com>
>> Cc: Siyuan Fu <siyuan.fu@intel.com>
>> Signed-off-by: Maciej Rabeda <maciej.rabeda@linux.intel.com>
>> Reviewed-by: Siyuan Fu <siyuan.fu@intel.com>
>> Tested-by: Laszlo Ersek <lersek@redhat.com>
>> Fixes: 9c20342eed70ec99ec50cd73cb81804299f05403
>> ---
>>   NetworkPkg/Ip6Dxe/Ip6Nd.c | 6 +++---
>>   1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/NetworkPkg/Ip6Dxe/Ip6Nd.c b/NetworkPkg/Ip6Dxe/Ip6Nd.c
>> index fd7f60b2f92c..0780a98cb325 100644
>> --- a/NetworkPkg/Ip6Dxe/Ip6Nd.c
>> +++ b/NetworkPkg/Ip6Dxe/Ip6Nd.c
>> @@ -2111,7 +2111,7 @@ Ip6ProcessRouterAdvertise (
>>         // Option size validity ensured by Ip6IsNDOptionValid().
>>
>>         //
>>
>>         ASSERT (LinkLayerOption.Length != 0);
>>
>> -      ASSERT (Offset + (UINT32) LinkLayerOption.Length * 8 >= (UINT32) Head-
>>> PayloadLength);
>> +      ASSERT (Offset + (UINT32) LinkLayerOption.Length * 8 <= (UINT32)
>> Head->PayloadLength);
>>
>>
>>
>>         ZeroMem (&LinkLayerAddress, sizeof (EFI_MAC_ADDRESS));
>>
>>         CopyMem (&LinkLayerAddress, LinkLayerOption.EtherAddr, 6);
>>
>> @@ -2164,7 +2164,7 @@ Ip6ProcessRouterAdvertise (
>>         // Option size validity ensured by Ip6IsNDOptionValid().
>>
>>         //
>>
>>         ASSERT (PrefixOption.Length == 4);
>>
>> -      ASSERT (Offset + (UINT32) PrefixOption.Length * 8 >= (UINT32) Head-
>>> PayloadLength);
>> +      ASSERT (Offset + (UINT32) PrefixOption.Length * 8 <= (UINT32) Head-
>>> PayloadLength);
>>
>>
>>         PrefixOption.ValidLifetime     = NTOHL (PrefixOption.ValidLifetime);
>>
>>         PrefixOption.PreferredLifetime = NTOHL
>> (PrefixOption.PreferredLifetime);
>>
>> @@ -2334,7 +2334,7 @@ Ip6ProcessRouterAdvertise (
>>         // Option size validity ensured by Ip6IsNDOptionValid().
>>
>>         //
>>
>>         ASSERT (MTUOption.Length == 1);
>>
>> -      ASSERT (Offset + (UINT32) MTUOption.Length * 8 >= (UINT32) Head-
>>> PayloadLength);
>> +      ASSERT (Offset + (UINT32) MTUOption.Length * 8 <= (UINT32) Head-
>>> PayloadLength);
>>
>>
>>         //
>>
>>         // Use IPv6 minimum link MTU 1280 bytes as the maximum packet size in
>> order
>>
>> --
>> 2.24.0.windows.2
>
> 
>


      reply	other threads:[~2020-04-03 12:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-02  9:14 [PATCH v2] NetworkPkg/Ip6Dxe: Fix ASSERT logic in Ip6ProcessRouterAdvertise() Maciej Rabeda
2020-04-03  7:21 ` Wu, Jiaxin
2020-04-03 12:36   ` Maciej Rabeda [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-list 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=22b2f78d-45bb-7b8b-c03d-17e0686478cb@linux.intel.com \
    --to=devel@edk2.groups.io \
    /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