Memory device with secure boot updates and self recovery
US-2024406008-A1 · Dec 5, 2024 · US
US10001984B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10001984-B2 |
| Application number | US-201615238944-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 17, 2016 |
| Priority date | Aug 17, 2016 |
| Publication date | Jun 19, 2018 |
| Grant date | Jun 19, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Embodiments of the present invention disclose a method, computer program product, and system for identifying software updates where a stack trace is received, the stack trace including a first set of metadata. An execution failure is determined to have occurred in the received stack trace, and in response, one or more software updates are received, the one or more software updates including a second set of metadata. One or more matching metadata in the first and second set of metadata is determined. A subset of software updates for display is generated, the subset of software updates being associated with matched metadata, and in response to receiving a selection input from a user, one or more software updates of the generated subset of software updates are executed.
Opening claim text (preview).
What is claimed is: 1. A computer implemented method for identifying software updates, the method comprising: receiving, by a processor, a stack trace, the stack trace including a first set of metadata; determining an execution failure in the received stack trace; receiving, by the processor, a plurality of software updates, the plurality of software updates including a second set of metadata associated with the execution failure; determining, by the processor, a subset of matching metadata, the subset of matching metadata including metadata from at least one of the first set of metadata and the second set of metadata, wherein determining the subset of matching metadata comprising: receiving a plurality of change logs associated with the plurality of software updates; generating a subset of the received plurality of change logs, the subset of change logs including change logs within a predetermined range, wherein the range includes at least a starting time stamp and an ending time stamp; parsing at least one of the change logs in the subset of change logs; and calculating a priority value associated with at least one of the change logs of the subset of parsed change logs, wherein the subset of matching metadata further comprises the at least one of the change logs and the corresponding priority value; generating, by the processor, a subset of software updates for display, the subset of software updates including software updates associated with the subset of matching metadata; and in response to receiving a selection input from a user, executing one or more software updates of the generated subset of software updates. 2. The method of claim 1 , wherein determining an execution failure further comprises: receiving a plurality of dump files; and generating a second stack trace based on the received dump files, determining an execution failure in the second stack trace. 3. The method of claim 1 , wherein metadata includes at least one of a set of location data and a change log. 4. The method of claim 1 , wherein determining a subset of matching metadata further comprises: determining build information associated with the received stack trace. 5. The method of claim 1 wherein the calculated priority value is based on a position in stack value, a number of lines value, or a modification date, or a combination thereof. 6. The method of claim 1 further comprising: at periodic intervals, determining that the generated subset of software updates includes software updates with a time stamp below a threshold; and executing the software updates with a time stamp below a threshold. 7. The method of claim 1 , further comprising: periodically monitoring for additional software updates in the plurality of software updates. 8. A computer program product for identifying software updates, the computer program product comprising: one or more computer-readable storage media and program instructions stored on the one or more computer-readable storage media, the program instructions comprising: instructions to receive a stack trace, the stack trace including a first set of metadata; instructions to determine an execution failure in the received stack trace; instructions to receive a plurality of software updates, the plurality of software updates including a second set of metadata associated with the execution failure; instructions to determine a subset of matching metadata, the subset of matching metadata including metadata from at least one of the first set of metadata and the second set of metadata, wherein instructions to determine the subset of matching metadata comprises: instructions to receive a plurality of change logs associated with the plurality of software updates; instructions to generate a subset of the received plurality of change logs, the subset of change logs including change logs within a predetermined range, wherein the range includes at least a starting time stamp and an ending time stamp; instructions to parse at least one of the change logs in the subset of change logs; and instructions to calculate a priority value associated with at least one of the change logs of the subset of parsed change logs, wherein the subset of matching metadata further comprises the at least one of the change logs and the corresponding priority value; instructions to generate a subset of software updates for display, the subset of software updates including software updates associated with the subset of matching metadata; and in response to receiving a selection input from a user, instructions to execute one or more software updates of the generated subset of software updates. 9. The computer program product of claim 8 , wherein determining an execution failure further comprises: instructions to receive a plurality of dump files; instructions to generate a second stack trace based on the received dump files; instructions to determine an execution failure in the second stack trace. 10. The computer program product of claim 8 , wherein metadata includes at least one of a set of location data and a change log. 11. The computer program product of claim 8 , wherein instructions to determine a subset of matching metadata further comprises: instructions to determine build information associated with the received stack trace. 12. The computer program product of claim 8 wherein the calculated priority value is based on a position in stack value, a number of lines value, or a modification date, or a combination thereof. 13. The computer program product of claim 8 further comprising: at periodic intervals, instructions to determine that the generated subset of software updates includes software updates with a time stamp below a threshold; and instructions to execute the software updates with a time stamp below a threshold. 14. The computer program product of claim 8 , further comprising: instructions to periodically monitor a database for additional software updates in the plurality of software updates. 15. A computer system for identifying software updates, the computer system comprising: one or more computer processors; one or more computer-readable storage media; and program instructions stored on the computer-readable storage media for execution by at least one of the one or more processors, the program instructions comprising: instructions to receive a stack trace, the stack trace including a first set of metadata; instructions to determine an execution failure in the received stack trace; instructions to receive a plurality of software updates, the plurality of software updates including a second set of metadata associated with the execution failure; instructions to determine a subset of matching metadata, the subset of matching metadata including metadata from at least one of the first set of metadata and the second set of metadata, wherein instructions to determine the subset of matching metadata comprises: instructions to receive a plurality of change logs associated with the plurality of software updates; instructions to generate a subset of the received plurality of change logs, the subset of change logs including change logs within a predetermined range, wherein the range includes at least a starting time stamp and an ending time stamp; instructions to parse at least one of the change logs in the subset of change logs; and instructions to calculate a priority value associated with at least one of the change logs of the subset of parsed change logs, wherein the subset of matching metadata further comprises the at least one of the change logs and the corresponding pr
Physics · mapped topic
Updates (security arrangements therefor G06F21/57) · CPC title
Physics · mapped topic
Incremental updates; Differential updates · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.