IP Library Patent Application 19016170
Patent Application
App. No. 19/016,170

SYSTEMS AND METHODS FOR CRASH ARTIFACT STORAGE AND RETRIEVAL

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 None
App. No.
19/016,170
Abstract

A system identifies one or more designated memory areas for temporary crash data storage using at least one predefined rule. In response to detecting a system failure event, the system captures and writes crash data to the one or more designated memory areas, wherein the system failure event triggers a reboot. Subsequent to the reboot, the system retrieves the crash data from the one or more designated memory areas. The system performs an integrity check on the retrieved crash data. In response to determining that the integrity check is successful, the system stores the retrieved crash data in a file system.

Claims (37)

1 . A method for crash artifact storage and retrieval, the method comprising:

identifying one or more designated memory areas for temporary crash data storage using at least one predefined rule;

in response to detecting a system failure event, capturing and writing crash data to the one or more designated memory areas, wherein the system failure event triggers a reboot;

subsequent to the reboot, retrieving the crash data from the one or more designated memory areas;

performing an integrity check on the retrieved crash data; and

in response to determining that the integrity check is successful, storing the retrieved crash data in a file system.

2 . The method of claim 1 , further comprising preventing redundant data storage by clearing signatures of the crash data from the one or more designated memory areas.

3 . The method of claim 2 , wherein the signatures comprise one or more of: data integrity markers, unique identifiers, metadata, and security tokens of the crash data.

4 . The method of claim 1 , wherein the one or more designated memory areas are located across a plurality of nodes in a computing environment, and wherein the system failure event occurs at a first node of the plurality of nodes.

5 . The method of claim 4 , wherein the one or more designated memory areas are a set of pages in each memory allocator list across all the plurality of nodes.

6 . The method of claim 5 , wherein the set of pages are pages at an end of each memory allocator list.

7 . The method of claim 1 , wherein the reboot is a warm reboot on a computing device.

8 . The method of claim 1 , wherein the reboot is a guest operating system reboot of a virtual machine and a hypervisor performs consistent memory allocation for the virtual machine.

9 . The method of claim 1 , wherein the retrieved crash data is stored in a storage location within the file system as selected by a user.

10 . The method of claim 1 , wherein the system failure event is a system panic.

11 . A system for crash artifact storage and retrieval, comprising:

at least one memory; and

at least one hardware processor coupled with the at least one memory and configured, individually or in combination, to:

identify, in the at least one memory, one or more designated memory areas for temporary crash data storage using at least one predefined rule;

in response to detecting a system failure event, capture and write crash data to the one or more designated memory areas, wherein the system failure event triggers a reboot;

subsequent to the reboot, retrieve the crash data from the one or more designated memory areas;

perform an integrity check on the retrieved crash data; and

in response to determining that the integrity check is successful, store the retrieved crash data in a file system.

12 . The system of claim 11 , wherein the at least one hardware processor is further configured to prevent redundant data storage by clearing signatures of the crash data from the one or more designated memory areas.

13 . The system of claim 12 , wherein the signatures comprise one or more of: data integrity markers, unique identifiers, metadata, and security tokens of the crash data.

14 . The system of claim 11 , wherein the one or more designated memory areas are located across a plurality of nodes in a computing environment, and wherein the system failure event occurs at a first node of the plurality of nodes.

15 . The system of claim 14 , wherein the one or more designated memory areas are a set of pages in each memory allocator list across all the plurality of nodes.

16 . The system of claim 15 , wherein the set of pages are pages at an end of each memory allocator list.

17 . The system of claim 11 , wherein the reboot is a warm reboot on a computing device.

18 . The system of claim 11 , wherein the reboot is a guest operating system reboot of a virtual machine and a hypervisor performs consistent memory allocation for the virtual machine.

19 . The system of claim 11 , wherein the retrieved crash data is stored in a storage location within the file system as selected by a user.

20 . A non-transitory computer readable medium storing thereon computer executable instructions for crash artifact storage and retrieval, including instructions for:

identifying one or more designated memory areas for temporary crash data storage using at least one predefined rule;

in response to detecting a system failure event, capturing and writing crash data to the one or more designated memory areas, wherein the system failure event triggers a reboot;

subsequent to the reboot, retrieving the crash data from the one or more designated memory areas;

performing an integrity check on the retrieved crash data; and

in response to determining that the integrity check is successful, storing the retrieved crash data in a file system.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 20, 2026
From: CLOUD LINUX SOFTWARE, INC.
To: TUXCARE, INC.
Reel/Frame 075718/0502 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 10, 2025
From: SELETSKIY, IGOR; NESTERENKO, ALEKSANDR
To: CLOUD LINUX SOFTWARE, INC.
Reel/Frame 069814/0187 →