Messages in this thread | | | Subject | Re: [PATCHv5 05/19] mm/page_alloc: Handle allocation for encrypted memory | From | Dave Hansen <> | Date | Thu, 19 Jul 2018 07:05:36 -0700 |
| |
On 07/19/2018 01:27 AM, Kirill A. Shutemov wrote: >> What other code might need prep_encrypted_page()? > > Custom pages allocators if these pages can end up in encrypted VMAs. > > It this case compaction creates own pool of pages to be used for > allocation during page migration.
OK, that makes sense. It also sounds like some great information to add near prep_encrypted_page().
Do we have any ability to catch cases like this if we get them wrong, or will we just silently corrupt data?
| |