IP Library Granted Patent US 10,621,112
Granted Patent B2
US 10,621,112 · App. 15/880,191 · Granted Apr 14, 2020

System and method of identifying a device driver

Inventor: Rui Shi (Cedar Park, TX)
Assignee: Dell Products L.P.
G06F13/102G06F9/4411G06F11/0793
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,621,112
App. No.
15/880,191
Granted
Apr 14, 2020
Kind
B2
Abstract

In one or more embodiments, one or more systems, methods, and processes determine an address of a memory medium of an information handling system associated with an exception; determine respective address spaces of the device drivers loaded in the memory medium; determine an address space of address spaces that includes the address associated with the exception; determine a device driver of the device drivers based at least on the address space; query the device driver for an identification of the device driver; determine if the device driver provides the identification of the device driver; if the device driver provides the identification of the device driver, output the identification of the device driver and exception information associated with the exception; and if the device driver does not provide the identification of the device driver, search for identification information of the device driver within the address space.

Claims (62)

1. An information handling system, comprising:

at least one processor; and

a memory medium that is coupled to the at least one processor and that includes processor instructions executed by the at least one processor to cause the information handling system to:

determine that an exception occurred, wherein at least one of an invalid pointer, an invalid pointer dereference, and a memory corruption causes the exception;

determine a particular address of the memory medium associated with the exception;

determine a plurality of device drivers loaded in the memory medium;

identify a plurality of respective address spaces of the plurality of device drivers;

determine an address space of the plurality of address spaces that includes the particular address of the memory medium associated with the exception;

identify a particular device driver of the plurality of device drivers based at least on the particular address space;

query the particular device driver for an identification of the particular device driver;

in response to the query, determine whether the particular device driver provides the identification of the particular device driver;

in response to determining that the particular device driver provides the identification of the particular device driver, output the identification of the particular device driver and exception information associated with the exception, the exception information including information associated with one or more states of the information handling system;

in response to determining that the particular device driver does not provide the identification of the particular device driver:

search for identification information of the particular device driver within the address space;

determine the identification information associated with the particular device driver; and

output the identification information of the particular device driver and the exception information associated with the exception, including outputting the information associated with the one or more states of the information handling system; and

wherein the information associated with the one or more states of the information handling system includes one or more of an exception reason, source information, a snapshot of one or more registers, one or more previous branch records, previous branch information, a call stack up to the exception, a stack dump, a list of one or more Unified Extensible Firmware Interface events triggered prior to the exception, and a list of one or more firmware drivers currently stored by the memory medium of the information handling system.

2. The information handling system of claim 1 , wherein, to search for the identification information associated with the particular device driver within the particular address space, the processor instructions further cause the information handling system to search for a string of American Standard Code for Information Interchange (ASCII) characters.

3. The information handling system of claim 2 , wherein, to search for the string of ASCII characters, the processor instructions further cause the information handling system to search for copyright information.

4. The information handling system of claim 2 , wherein, to search for the string of ASCII characters, the processor instructions further cause the information handling system to start a search at a beginning of the address space.

5. The information handling system of claim 2 , wherein all characters of the string of ASCII characters are printable.

6. The information handling system of claim 1 , wherein, in response to determining that the particular device driver provides the identification of the particular device driver, the processor instructions further cause the information handling system to determine that the particular device driver supports Efi Component Name2 Protocol.

7. A method, comprising:

determining that an exception occurred, wherein at least one of an invalid pointer, an invalid pointer dereference, and a memory corruption causes the exception;

determining a particular address of a memory medium of an information handling system associated with the exception;

determining a plurality of device drivers loaded in the memory medium of the information handling system;

identify a plurality of respective address spaces of the plurality of device drivers;

determine an address space of the plurality of address spaces that includes the particular address of the memory medium associated with the exception;

identifying a particular device driver of the plurality of device drivers based at least on the particular address space;

querying the particular device driver for an identification of the particular device driver;

in response to the query, determining whether the particular device driver provides the identification of the particular device driver;

in response to determining that the particular device driver provides the identification of the particular device driver, output the identification of the particular device driver and exception information associated with the exception, the exception information including information associated with one or more states of the information handling system;

in response to determining that the particular device driver does not provide the identification of the particular device driver:

searching for the identification of the particular device driver within the address space;

determining the identification of the particular device driver; and

outputting the identification of the particular device driver and the exception information associated with the exception, including outputting the information associated with the one or more states of the information handling system; and

wherein the information associated with the one or more states of the information handling system includes one or more of an exception reason, source information, a snapshot of one or more registers, one or more previous branch records, previous branch information, a call stack up to the exception, a stack dump, a list of one or more Unified Extensible Firmware Interface events triggered prior to the exception, and a list of one or more firmware drivers currently stored by the memory medium of the information handling system.

8. The method of claim 7 , wherein the searching for the identification of the particular device driver within the particular address space includes searching for a string of American Standard Code for Information Interchange (ASCII) characters.

9. The method of claim 8 , wherein the searching for the string of ASCII characters, includes searching for copyright information.

10. The method of claim 8 , wherein the searching for the string of ASCII characters, includes starting a search at a beginning of the address space.

11. The method of claim 8 , wherein all characters of the string of ASCII characters are printable.

12. The method of claim 7 , wherein, in response to determining that the particular device driver provides the identification of the particular device driver includes determining if the device driver supports Efi Component Name2 Protocol.

13. A computer-readable non-transitory memory medium that includes processor instructions executed by at least one processor of an information handling system to cause the information handling system to:

determine that an exception occurred, wherein at least one of an invalid pointer, an invalid pointer dereference, and a memory corruption causes the exception;

determine a particular address of the memory medium associated with the exception;

determine a plurality of device drivers loaded in the memory medium;

identify a plurality of respective address spaces of the plurality of device drivers;

determine an address space of the plurality of address spaces that includes the particular address of the memory medium associated with the exception;

identify a particular device driver of the plurality of device drivers based at least on the particular address space;

query the particular device driver for an identification of the particular device driver;

in response to the query, determine whether the particular device driver provides the identification of the particular device driver;

in response to determining that the particular device driver provides the identification of the particular device driver, output the identification of the particular device driver and exception information associated with the exception, the exception information including information associated with one or more states of the information handling system;

in response to determining that the particular device driver does not provide the identification of the particular device driver:

search for identification information of the particular device driver within the address space;

determine the identification information associated with the particular device driver; and

output the identification information of the particular device driver and the exception information associated with the exception, including outputting the information associated with the one or more states of the information handling system; and

wherein the information associated with the one or more states of the information handling system includes one or more of an exception reason, source information, a snapshot of one or more registers, one or more previous branch records, previous branch information, a call stack up to the exception, a stack dump, a list of one or more Unified Extensible Firmware Interface events triggered prior to the exception, and a list of one or more firmware drivers currently stored by the memory medium of the information handling system.

14. The computer-readable non-transitory memory medium of claim 13 , wherein, to search for the identification information associated with the particular device driver within the particular address space, the processor instructions further cause the information handling system to search for a string of American Standard Code for Information Interchange (ASCII) characters.

15. The computer-readable non-transitory memory medium of claim 14 , wherein, to search for the string of ASCII characters, the processor instructions further cause the information handling system to search for copyright information.

16. The computer-readable non-transitory memory medium of claim 14 , wherein, to search for the string of ASCII characters, the processor instructions further cause the information handling system to start a search at a beginning of the address space.

17. The computer-readable non-transitory memory medium of claim 14 , wherein all characters of the string of ASCII characters are printable.

18. The computer-readable non-transitory memory medium of claim 13 , wherein, in response to determining that the device driver provides the identification of the particular device driver, the processor instructions further cause the information handling system to determine that the particular device driver supports Efi Component Name2 Protocol.

Assignments (8)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053546/0001) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC IP HOLDING COMPANY LLC
Reel/Frame 071642/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045482/0131) Recorded May 20, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO WYSE TECHNOLOGY L.L.C.)
Reel/Frame 061749/0924 →
RELEASE OF SECURITY INTEREST AT REEL 045482 FRAME 0395 Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; WYSE TECHNOLOGY L.L.C.
Reel/Frame 058298/0314 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
SECURITY AGREEMENT Recorded Mar 21, 2019
From: CREDANT TECHNOLOGIES, INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 049452/0223 →
PATENT SECURITY AGREEMENT (NOTES) Recorded Mar 1, 2018
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; WYSE TECHNOLOGY L.L.C.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 045482/0131 →
PATENT SECURITY AGREEMENT (CREDIT) Recorded Mar 1, 2018
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; WYSE TECHNOLOGY L.L.C.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 045482/0395 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 25, 2018
From: SHI, RUI
To: DELL PRODUCTS L.P.
Reel/Frame 044732/0331 →
Continuity (1)
Related Publication 20190227954A1 · Jul 25, 2019