public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Dandan Bi" <dandan.bi@intel.com>
To: "Ma, Hua" <hua.ma@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Wang, Jian J" <jian.j.wang@intel.com>,
	Liming Gao <gaoliming@byosoft.com.cn>
Subject: Re: [PATCH] MdeModulePkg/Core/Dxe: Add lock protection in CoreLocateHandleBuffer()
Date: Fri, 8 Oct 2021 01:39:40 +0000	[thread overview]
Message-ID: <DM4PR11MB54539E5A67ED58C2B072AAB8EAB29@DM4PR11MB5453.namprd11.prod.outlook.com> (raw)
In-Reply-To: <33349c0e687ed186cd13db413fa708a8b761ffea.1632894508.git.hua.ma@intel.com>

Reviewed-by: Dandan Bi <dandan.bi@intel.com>



Thanks,
Dandan

> -----Original Message-----
> From: Ma, Hua <hua.ma@intel.com>
> Sent: Wednesday, September 29, 2021 1:49 PM
> To: devel@edk2.groups.io
> Cc: Ma, Hua <hua.ma@intel.com>; Wang, Jian J <jian.j.wang@intel.com>;
> Liming Gao <gaoliming@byosoft.com.cn>; Bi, Dandan <dandan.bi@intel.com>
> Subject: [PATCH] MdeModulePkg/Core/Dxe: Add lock protection in
> CoreLocateHandleBuffer()
> 
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3666
> 
> Currently, CoreLocateHandleBuffer() follows three steps:
> 1) get the size of protocol database firstly
> 2) allocate the buffer based on the size
> 3) get the protocol database into the buffer There is no lock protection for
> the whole three steps. If a new protocol added in step 2) by other task, e.g.
> (event timer handle USB device hotplug). The size of protocol database may
> be increased and cannot fit into the previous buffer in step 3). The protocol
> database cannot be returned successfully, EFI_BUFFER_TOO_SMALL error
> will be returned.
> 
> This patch adds the lock to protect the whole three steps.
> It can make sure the correct protocol database be returned.
> 
> Cc: Jian J Wang <jian.j.wang@intel.com>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
> Cc: Dandan Bi <dandan.bi@intel.com>
> Signed-off-by: Hua Ma <hua.ma@intel.com>
> ---
>  MdeModulePkg/Core/Dxe/Hand/Locate.c | 64
> +++++++++++++++++++++++------
>  1 file changed, 51 insertions(+), 13 deletions(-)
> 
> diff --git a/MdeModulePkg/Core/Dxe/Hand/Locate.c
> b/MdeModulePkg/Core/Dxe/Hand/Locate.c
> index be17f4cbc3..4987c046c6 100644
> --- a/MdeModulePkg/Core/Dxe/Hand/Locate.c
> +++ b/MdeModulePkg/Core/Dxe/Hand/Locate.c
> @@ -86,7 +86,8 @@ CoreGetNextLocateByProtocol (
> 
> 
>  /**
> -  Locates the requested handle(s) and returns them in Buffer.
> +  Internal function for locating the requested handle(s) and returns them in
> Buffer.
> +  The caller should already have acquired the ProtocolLock.
> 
>    @param  SearchType             The type of search to perform to locate the
>                                   handles @@ -104,8 +105,7 @@
> CoreGetNextLocateByProtocol (
> 
>  **/
>  EFI_STATUS
> -EFIAPI
> -CoreLocateHandle (
> +InternalCoreLocateHandle (
>    IN EFI_LOCATE_SEARCH_TYPE   SearchType,
>    IN EFI_GUID                 *Protocol   OPTIONAL,
>    IN VOID                     *SearchKey  OPTIONAL,
> @@ -143,11 +143,6 @@ CoreLocateHandle (
>    ResultBuffer = (IHANDLE **) Buffer;
>    Status = EFI_SUCCESS;
> 
> -  //
> -  // Lock the protocol database
> -  //
> -  CoreAcquireProtocolLock ();
> -
>    //
>    // Get the search function based on type
>    //
> @@ -190,7 +185,6 @@ CoreLocateHandle (
>    }
> 
>    if (EFI_ERROR(Status)) {
> -    CoreReleaseProtocolLock ();
>      return Status;
>    }
> 
> @@ -247,10 +241,47 @@ CoreLocateHandle (
>      }
>    }
> 
> -  CoreReleaseProtocolLock ();
>    return Status;
>  }
> 
> +/**
> +  Locates the requested handle(s) and returns them in Buffer.
> +
> +  @param  SearchType             The type of search to perform to locate the
> +                                 handles
> +  @param  Protocol               The protocol to search for
> +  @param  SearchKey              Dependant on SearchType
> +  @param  BufferSize             On input the size of Buffer.  On output the
> +                                 size of data returned.
> +  @param  Buffer                 The buffer to return the results in
> +
> +  @retval EFI_BUFFER_TOO_SMALL   Buffer too small, required buffer size is
> +                                 returned in BufferSize.
> +  @retval EFI_INVALID_PARAMETER  Invalid parameter
> +  @retval EFI_SUCCESS            Successfully found the requested handle(s)
> and
> +                                 returns them in Buffer.
> +
> +**/
> +EFI_STATUS
> +EFIAPI
> +CoreLocateHandle (
> +  IN EFI_LOCATE_SEARCH_TYPE   SearchType,
> +  IN EFI_GUID                 *Protocol   OPTIONAL,
> +  IN VOID                     *SearchKey  OPTIONAL,
> +  IN OUT UINTN                *BufferSize,
> +  OUT EFI_HANDLE              *Buffer
> +  )
> +{
> +  EFI_STATUS Status;
> +
> +  //
> +  // Lock the protocol database
> +  //
> +  CoreAcquireProtocolLock ();
> +  Status = InternalCoreLocateHandle(SearchType, Protocol, SearchKey,
> +BufferSize, Buffer);
> +  CoreReleaseProtocolLock ();
> +  return Status;
> +}
> 
> 
>  /**
> @@ -610,7 +641,6 @@ Done:
>    return Status;
>  }
> 
> -
>  /**
>    Function returns an array of handles that support the requested protocol
>    in a buffer allocated from pool. This is a version of CoreLocateHandle() @@
> -657,7 +687,12 @@ CoreLocateHandleBuffer (
>    BufferSize = 0;
>    *NumberHandles = 0;
>    *Buffer = NULL;
> -  Status = CoreLocateHandle (
> +
> +  //
> +  // Lock the protocol database
> +  //
> +  CoreAcquireProtocolLock();
> +  Status = InternalCoreLocateHandle (
>               SearchType,
>               Protocol,
>               SearchKey,
> @@ -674,15 +709,17 @@ CoreLocateHandleBuffer (
>      if (Status != EFI_INVALID_PARAMETER) {
>        Status = EFI_NOT_FOUND;
>      }
> +    CoreReleaseProtocolLock ();
>      return Status;
>    }
> 
>    *Buffer = AllocatePool (BufferSize);
>    if (*Buffer == NULL) {
> +    CoreReleaseProtocolLock ();
>      return EFI_OUT_OF_RESOURCES;
>    }
> 
> -  Status = CoreLocateHandle (
> +  Status = InternalCoreLocateHandle (
>               SearchType,
>               Protocol,
>               SearchKey,
> @@ -695,6 +732,7 @@ CoreLocateHandleBuffer (
>      *NumberHandles = 0;
>    }
> 
> +  CoreReleaseProtocolLock ();
>    return Status;
>  }
> 
> --
> 2.32.0.windows.2


  reply	other threads:[~2021-10-08  1:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29  5:49 [PATCH] MdeModulePkg/Core/Dxe: Add lock protection in CoreLocateHandleBuffer() Ma, Hua
2021-10-08  1:39 ` Dandan Bi [this message]
2021-10-08  2:47   ` 回复: " gaoliming

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=DM4PR11MB54539E5A67ED58C2B072AAB8EAB29@DM4PR11MB5453.namprd11.prod.outlook.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