Updating an operating system image using binary large object files

US2025291571A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2025291571-A1
Application numberUS-202418604601-A
CountryUS
Kind codeA1
Filing dateMar 14, 2024
Priority dateMar 14, 2024
Publication dateSep 18, 2025
Grant date

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Techniques for atomic live updates to operating systems are described herein. For example, a computing system can generate a first version of a binary large object (BLOB) file indicating first metadata for each file of a first version of an image for an operating system. The computing system can generate a second version of the BLOB file indicating second metadata for each file of a second version of the image. The second version can include new files associated with an update to the operating system. The computing system can execute the update to the operating system by remounting, by a file system for the operating system, the second version of the image of the operating system using the second metadata of the second version of the BLOB file.

First claim

Opening claim text (preview).

What is claimed is: 1 . A system comprising: a processing device; and a non-transitory memory comprising instructions that are executable by the processing device for causing the processing device to: generate a first version of a binary large object (BLOB) file indicating first metadata for each file of a first version of an image for an operating system; generate a second version of the BLOB file indicating second metadata for each file of a second version of the image, wherein the second version comprises a plurality of new files associated with an update to the operating system; and execute the update to the operating system by remounting, by a file system for the operating system, the second version of the image of the operating system using the second metadata from the second version of the BLOB file. 2 . The system of claim 1 , wherein the memory further comprises instructions that are executable by the processing device for causing the processing device to: identify a first set of services having access to the plurality of new files subsequent to execution of the update; stop execution of the first set of services prior to remounting the second version of the image of the operating system; and restart execution of the first set of services subsequent to remounting the second version of the image of the operating system. 3 . The system of claim 2 , wherein the memory further comprises instructions that are executable by the processing device for causing the processing device to: identify a second set of services lacking access to the plurality of new files subsequent to execution of the update; and continue execution of the second set of services while remounting the second version of the image of the operating system. 4 . The system of claim 1 , wherein the memory further comprises instructions that are executable by the processing device for causing the processing device to, prior to generating the first version of the BLOB file: mount, by the file system, the first version of the image of the operating system. 5 . The system of claim 1 , wherein the first metadata or the second metadata comprises, for each file of the operating system, a location of the file, and wherein the memory further comprises instructions that are executable by the processing device for causing the processing device to execute the update to the operating system by: switching from accessing a file via a first location indicated by the first metadata of the first version of the BLOB file to a second location indicated by the second metadata of the second version of the BLOB file. 6 . The system of claim 1 , wherein the memory further comprises instructions that are executable by the processing device for causing the processing device to execute the update to the operating system while running the operating system. 7 . The system of claim 1 , wherein the file system has a same mount identifier used by the operating system prior to execution of the update and subsequent to execution of the update. 8 . A method comprising: generating, by a processing device, a first version of a binary large object (BLOB) file indicating first metadata for each file of a first version of an image for an operating system; generating, by the processing device, a second version of the BLOB file indicating second metadata for each file of a second version of the image, wherein the second version comprises a plurality of new files associated with an update to the operating system; and executing the update to the operating system by remounting, by the processing device executing a file system for the operating system, the second version of the image of the operating system using the second metadata of the second version of the BLOB file. 9 . The method of claim 8 , further comprising: identifying a first set of services having access to the plurality of new files subsequent to execution of the update; stopping execution of the first set of services prior to remounting the second version of the image of the operating system; and restarting execution of the first set of services subsequent to remounting the second version of the image of the operating system. 10 . The method of claim 9 , further comprising: identifying a second set of services lacking access to the plurality of new files subsequent to execution of the update; and continuing execution of the second set of services while remounting the second version of the image of the operating system. 11 . The method of claim 8 , further comprising, prior to generating the first version of the BLOB file: mounting, by the file system, the first version of the image of the operating system. 12 . The method of claim 8 , wherein the first metadata or the second metadata comprises, for each file of the operating system, a location of the file, and wherein executing the update to the operating system further comprises: switching from accessing a file via a first location indicated by the first metadata of the first version of the BLOB file to a second location indicated by the second metadata of the second version of the BLOB file. 13 . The method of claim 8 , further comprising executing the update to the operating system while running the operating system. 14 . The method of claim 8 , wherein the file system has a same mount identifier used by the operating system prior to execution of the update and subsequent to execution of the update. 15 . A non-transitory computer-readable medium comprising program code that is executable by a processing device for causing the processing device to: generate a first version of a binary large object (BLOB) file indicating first metadata for each file of a first version of an image for an operating system; generate a second version of the BLOB file indicating second metadata for each file of a second version of the image, wherein the second version comprises a plurality of new files associated with an update to the operating system; and execute the update to the operating system by remounting, by a file system for the operating system, the second version of the image of the operating system using the second metadata of the second version of the BLOB file. 16 . The non-transitory computer-readable medium of claim 15 , wherein the program code is further executable by the processing device for causing the processing device to: identify a first set of services having access to the plurality of new files subsequent to execution of the update; stop execution of the first set of services prior to remounting the second version of the image of the operating system; and restart execution of the first set of services subsequent to remounting the second version of the image of the operating system. 17 . The non-transitory computer-readable medium of claim 16 , wherein the program code is further executable by the processing device for causing the processing device to: identify a second set of services lacking access to the plurality of new files subsequent to execution of the update; and continue execution of the second set of services while remounting the second version of the image of the operating system. 18 . The non-transitory computer-readable medium of claim 15 , wherein the program code is further executable by the processing device for causing the processing device to, prior to generating the first version of the BLOB file: mount, by the file system, the first version of the image of the operating system. 19 . The non-t

Assignees

Inventors

Classifications

  • G06F8/65Primary

    Updates (security arrangements therefor G06F21/57) · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US2025291571A1 cover?
Techniques for atomic live updates to operating systems are described herein. For example, a computing system can generate a first version of a binary large object (BLOB) file indicating first metadata for each file of a first version of an image for an operating system. The computing system can generate a second version of the BLOB file indicating second metadata for each file of a second vers…
Who is the assignee on this patent?
Red Hat Inc
What technology area does this patent fall under?
Primary CPC classification G06F8/65. Mapped technology areas include Physics.
When was this patent published?
Publication date Thu Sep 18 2025 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 4 related publications on this page (citations in our corpus or others sharing the same primary CPC).