public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Zeng, Star" <star.zeng@intel.com>
To: "amit.ak@samsung.com" <amit.ak@samsung.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Gao, Liming" <liming.gao@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "Zeng, Star" <star.zeng@intel.com>
Subject: Re: [PATCH V3] MdeModulePkg/DxeCore: Fixed Interface returned by CoreOpenProtocol
Date: Thu, 22 Jun 2017 13:07:37 +0000	[thread overview]
Message-ID: <0C09AFA07DD0434D9E2A0C6AEB0483103B8EC647@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20170622125419epcms5p3849260b8c26f233522e160c9a346933e@epcms5p3>

Amit,

If consumer calls OpenProtocol with Attributes = EFI_OPEN_PROTOCOL_TEST_PROTOCOL and Interface = NULL, and the protocol could not be found, how could the code with the patch work to assign *Interface = NULL?

And also UEFI spec has words Interface will be ignored if Attributes is EFI_OPEN_PROTOCOL_TEST_PROTOCOL.
“InterfaceSupplies the address where a pointer to the corresponding Protocol Interface is returned. NULL will be returned in *Interface if a structure is not associated with Protocol. This parameter is optional, and will be ignored if Attributes is EFI_OPEN_PROTOCOL_TEST_PROTOCOL.”

Thanks,
Star
From: Amit Kumar [mailto:amit.ak@samsung.com]
Sent: Thursday, June 22, 2017 8:54 PM
To: edk2-devel@lists.01.org; Gao, Liming <liming.gao@intel.com>; Zeng, Star <star.zeng@intel.com>; Kinney, Michael D <michael.d.kinney@intel.com>
Cc: Tian, Feng <feng.tian@intel.com>
Subject: RE: RE: [edk2] [PATCH V3] MdeModulePkg/DxeCore: Fixed Interface returned by CoreOpenProtocol


>>Should the code
>>
>>+    // Return NULL Interface if Unsupported Protocol
>>+    *Interface = NULL;
>>
>>be
>>
>>+    if (Attributes != EFI_OPEN_PROTOCOL_TEST_PROTOCOL) {
>>+      // Return NULL Interface if Unsupported Protocol
>>+      *Interface = NULL;
>>+    }
>>
>>to cover the case Attributes = EFI_OPEN_PROTOCOL_TEST_PROTOCOL and Interface = NULL?
>>
>>
>>Thanks,
>>Star



Hello Star,



It looks like and you suggestion is apt and satisfies the use case scenarios of EFI_OPEN_PROTOCOL_TEST_PROTOCOL.

But if we talk of UEFI Spec 2.7, I think the patch is good enough .

I would like to have some suggestion here from all the concerned people, if agreed I would add these changes to the patch.



Thanks And Regards

Amit





--------- Original Message ---------

Sender : Zeng, Star <star.zeng@intel.com<mailto:star.zeng@intel.com>>

Date : 2017-06-20 15:28 (GMT+5:30)

Title : RE: [edk2] [PATCH V3] MdeModulePkg/DxeCore: Fixed Interface returned by CoreOpenProtocol

To : Amit Kumar<amit.ak@samsung.com<mailto:amit.ak@samsung.com>>, null<edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org>>

CC : null<liming.gao@intel.com<mailto:liming.gao@intel.com>>, null<star.zeng@intel.com<mailto:star.zeng@intel.com>>



Should the code



+    // Return NULL Interface if Unsupported Protocol

+    *Interface = NULL;



be



+    if (Attributes != EFI_OPEN_PROTOCOL_TEST_PROTOCOL) {

+      // Return NULL Interface if Unsupported Protocol

+      *Interface = NULL;

+    }



to cover the case Attributes = EFI_OPEN_PROTOCOL_TEST_PROTOCOL and Interface = NULL?





Thanks,

Star

-----Original Message-----

From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Amit Kumar

Sent: Monday, June 19, 2017 8:24 PM

To: edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org>

Cc: Tian, Feng <feng.tian@intel.com<mailto:feng.tian@intel.com>>

Subject: [edk2] [PATCH V3] MdeModulePkg/DxeCore: Fixed Interface returned by CoreOpenProtocol



Change Since v2:

1) Modified to use EFI_ERROR to get status code



Change since v1:

1) Fixed typo protocal to protocol

2) Fixed coding style



Modified source code to update Interface as per spec.

1) In case of Protocol is un-supported, interface should be returned NULL.

2) In case of any error, interface should not be modified.

3) In case of Test Protocol, interface is optional.



Contributed-under: TianoCore Contribution Agreement 1.0

Signed-off-by: Amit Kumar <amit.ak@samsung.com<mailto:amit.ak@samsung.com>>

---

 MdeModulePkg/Core/Dxe/Hand/Handle.c | 24 ++++++++++++------------

 1 file changed, 12 insertions(+), 12 deletions(-)



diff --git a/MdeModulePkg/Core/Dxe/Hand/Handle.c b/MdeModulePkg/Core/Dxe/Hand/Handle.c

index 1c25521..6de300f 100644

--- a/MdeModulePkg/Core/Dxe/Hand/Handle.c

+++ b/MdeModulePkg/Core/Dxe/Hand/Handle.c

@@ -1004,12 +1004,8 @@ CoreOpenProtocol (

   //

   // Check for invalid Interface

   //

-  if (Attributes != EFI_OPEN_PROTOCOL_TEST_PROTOCOL) {

-    if (Interface == NULL) {

-      return EFI_INVALID_PARAMETER;

-    } else {

-      *Interface = NULL;

-    }

+  if ((Attributes != EFI_OPEN_PROTOCOL_TEST_PROTOCOL) && (Interface == NULL)) {

+    return EFI_INVALID_PARAMETER;

   }



   //

@@ -1073,15 +1069,11 @@ CoreOpenProtocol (

   Prot = CoreGetProtocolInterface (UserHandle, Protocol);

   if (Prot == NULL) {

     Status = EFI_UNSUPPORTED;

+    // Return NULL Interface if Unsupported Protocol

+    *Interface = NULL;

     goto Done;

   }



-  //

-  // This is the protocol interface entry for this protocol

-  //

-  if (Attributes != EFI_OPEN_PROTOCOL_TEST_PROTOCOL) {

-    *Interface = Prot->Interface;

-  }

   Status = EFI_SUCCESS;



   ByDriver        = FALSE;

@@ -1175,6 +1167,14 @@ CoreOpenProtocol (

   }



 Done:

+

+  //

+  // This is the protocol interface entry for this protocol.

+  // In case of any Error, Interface should not be updated as per spec.

+  //

+  if (!EFI_ERROR (Status) && Attributes != EFI_OPEN_PROTOCOL_TEST_PROTOCOL) {

+    *Interface = Prot->Interface;

+  }

   //

   // Done. Release the database lock are return

   //

--

1.9.1



_______________________________________________

edk2-devel mailing list

edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org>

https://lists.01.org/mailman/listinfo/edk2-devel



[cid:image001.png@01D2EB9B.0901B210]

[http://ext.samsung.net/mail/ext/v1/external/status/update?userid=amit.ak&do=bWFpbElEPTIwMTcwNjIyMTI1NDE5ZXBjbXM1cDM4NDkyNjBiOGMyNmYyMzM1MjJlMTYwYzlhMzQ2OTMzZSZyZWNpcGllbnRBZGRyZXNzPXN0YXIuemVuZ0BpbnRlbC5jb20_]

      parent reply	other threads:[~2017-06-22 13:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170619122254epcas5p49c12385e361c09d50eb4d0dfea71f41a@epcas5p4.samsung.com>
2017-06-19 12:23 ` [PATCH V3] MdeModulePkg/DxeCore: Fixed Interface returned by CoreOpenProtocol Amit Kumar
2017-06-19 14:41   ` Gao, Liming
2017-06-20  9:58   ` Zeng, Star
     [not found]   ` <CGME20170619122254epcas5p49c12385e361c09d50eb4d0dfea71f41a@epcms5p3>
     [not found]     ` <20170622125419epcms5p3849260b8c26f233522e160c9a346933e@epcms5p3>
2017-06-22 13:07       ` Zeng, Star [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=0C09AFA07DD0434D9E2A0C6AEB0483103B8EC647@shsmsx102.ccr.corp.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