mm: option to _always_ scrub freed domheap pages
PATCH v2 1/1 mm: option to _always_ scrub freed domheap pages
Give the administrator further control on when to scrub domheap pages by adding an option to always scrub. This is a safety feature that, when enabled, prevents a (buggy) domain from leaking secrets if it accidentally frees a page without proper scrubbing.
---
Changes in v2:
- Renamed parameter to scrub-domheap, and now at the right place
- Used "bool __read_mostly", no zero init, and correct comment style
- Added George's A-b
--- docs/misc/xen-command-line.pandoc | 8 ++++++++ xen/common/page_alloc.c | 9 +++++++-- 2 files changed, 15 insertions(+), 2 deletions(-)
docs/misc/xen-command-line.pandoc +8 -0
@@ -1779,6 +1779,14 @@ sockets, &c. This will reduce performance somewhat, particularly on systems with hyperthreading enabled, but should reduce power by enabling more sockets and cores to go into deeper sleep states. +### scrub-domheap +> `= <boolean>` + +> Default: `false` + +Scrub domains' freed pages. This is a safety net against a (buggy) domain +accidentally leaking secrets by releasing pages without proper sanitization. + ### serial_tx_buffer > `= <size>`
xen/common/page_alloc.c +7 -2
@@ -214,6 +214,10 @@ custom_param("bootscrub", parse_bootscrub_param);static unsigned long __initdata opt_bootscrub_chunk =MB (128 );size_param ("bootscrub_chunk" , opt_bootscrub_chunk); +/* scrub-domheap -> Domheap pages are scrubbed when freed */ +static bool __read_mostly opt_scrub_domheap; +boolean_param ("scrub-domheap" , opt_scrub_domheap); +#ifdef CONFIG_SCRUB_DEBUG static bool __read_mostly scrub_debug;#else
@@ -2378,9 +2382,10 @@ void free_domheap_pages(struct page_info *pg, unsigned int order)/* * Normally we expect a domain to clear pages before freeing them, * if it cares about the secrecy of their contents. However, after -* a domain has died we assume responsibility for erasure. +* a domain has died we assume responsibility for erasure. We do +* scrub regardless if option scrub_domheap is set. */ - scrub = d->is_dying || scrub_debug; + scrub = d->is_dying || scrub_debug || opt_scrub_domheap; }else {
Signature · 7 lines
2.15.3.AMZN _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
xen/common/page_alloc.c custom_param("bootscrub", parse_bootscrub_param); · line 219
Quoted 10 lines
Quoted 1 line
Quoted 1 line · On 07.05.19 at 13:34, <[email protected]> wrote:
xen/common/page_alloc.c +3
-0@@ -214,6 +214,10 @@ custom_param("bootscrub", parse_bootscrub_param);static unsigned long __initdata opt_bootscrub_chunk =MB (128 );size_param ("bootscrub_chunk" , opt_bootscrub_chunk); +/* scrub-domheap -> Domheap pages are scrubbed when freed */ +static bool __read_mostly opt_scrub_domheap; +boolean_param ("scrub-domheap" , opt_scrub_domheap);
Upon 2nd thought this, btw, would seem to be an excellent candidate for becoming a runtime parameter.
xen/common/page_alloc.c void free_domheap_pages(struct page_info *pg, unsigned int order) · line 2388
Quoted 10 lines
xen/common/page_alloc.c +3
-2@@ -2378,9 +2382,10 @@ void free_domheap_pages(struct page_info *pg, unsigned int order)/* * Normally we expect a domain to clear pages before freeing them, * if it cares about the secrecy of their contents. However, after -* a domain has died we assume responsibility for erasure. +* a domain has died we assume responsibility for erasure. We do +* scrub regardless if option scrub_domheap is set. */ - scrub = d->is_dying || scrub_debug; + scrub = d->is_dying || scrub_debug || opt_scrub_domheap;
Did you consider setting opt_scrub_domheap when scrub_debug is set? This would shorten the (runtime) calculation here by a tiny bit, at the price of doing one more thing once while booting.
Jan
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Quoted 14 lines · Jan Beulich
xen/common/page_alloc.c custom_param("bootscrub", parse_bootscrub_param); · line 219
Quoted 10 lines
Quoted 1 line
Quoted 1 line · On 07.05.19 at 13:34, <[email protected]> wrote:
xen/common/page_alloc.c +3
-0@@ -214,6 +214,10 @@ custom_param("bootscrub", parse_bootscrub_param);static unsigned long __initdata opt_bootscrub_chunk =MB (128 );size_param ("bootscrub_chunk" , opt_bootscrub_chunk); +/* scrub-domheap -> Domheap pages are scrubbed when freed */ +static bool __read_mostly opt_scrub_domheap; +boolean_param ("scrub-domheap" , opt_scrub_domheap);Upon 2nd thought this, btw, would seem to be an excellent candidate for becoming a runtime parameter.
Quoted 14 lines
xen/common/page_alloc.c void free_domheap_pages(struct page_info *pg, unsigned int order) · line 2388
Quoted 10 lines
xen/common/page_alloc.c +3
-2@@ -2378,9 +2382,10 @@ void free_domheap_pages(struct page_info *pg, unsigned int order)/* * Normally we expect a domain to clear pages before freeing them, * if it cares about the secrecy of their contents. However, after -* a domain has died we assume responsibility for erasure. +* a domain has died we assume responsibility for erasure. We do +* scrub regardless if option scrub_domheap is set. */ - scrub = d->is_dying || scrub_debug; + scrub = d->is_dying || scrub_debug || opt_scrub_domheap;Did you consider setting
opt_scrub_domheapwhenscrub_debugis set? This would shorten the (runtime) calculation here by a tiny bit, at the price of doing one more thing once while booting.
Just for clarification Jan -- did you mean, "I'm happy for this to go in as it is, but if you feel like it, here are two improvements"?
-George
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Quoted 31 lines
Quoted 1 line
Quoted 1 line · On 07.05.19 at 15:15, <[email protected]> wrote:
Quoted 14 lines · Jan Beulich
xen/common/page_alloc.c custom_param("bootscrub", parse_bootscrub_param); · line 219
Quoted 10 lines
Quoted 1 line
Quoted 1 line · On 07.05.19 at 13:34, <[email protected]> wrote:
xen/common/page_alloc.c +3
-0@@ -214,6 +214,10 @@ custom_param("bootscrub", parse_bootscrub_param);static unsigned long __initdata opt_bootscrub_chunk =MB (128 );size_param ("bootscrub_chunk" , opt_bootscrub_chunk); +/* scrub-domheap -> Domheap pages are scrubbed when freed */ +static bool __read_mostly opt_scrub_domheap; +boolean_param ("scrub-domheap" , opt_scrub_domheap);Upon 2nd thought this, btw, would seem to be an excellent candidate for becoming a runtime parameter.
Quoted 14 lines
xen/common/page_alloc.c void free_domheap_pages(struct page_info *pg, unsigned int order) · line 2388
Quoted 10 lines
xen/common/page_alloc.c +3
-2@@ -2378,9 +2382,10 @@ void free_domheap_pages(struct page_info *pg, unsigned int order)/* * Normally we expect a domain to clear pages before freeing them, * if it cares about the secrecy of their contents. However, after -* a domain has died we assume responsibility for erasure. +* a domain has died we assume responsibility for erasure. We do +* scrub regardless if option scrub_domheap is set. */ - scrub = d->is_dying || scrub_debug; + scrub = d->is_dying || scrub_debug || opt_scrub_domheap;Did you consider setting
opt_scrub_domheapwhenscrub_debugis set? This would shorten the (runtime) calculation here by a tiny bit, at the price of doing one more thing once while booting.
Quoted 2 lines
Just for clarification Jan -- did you mean, "I'm happy for this to go in as it is, but if you feel like it, here are two improvements"?
Yes (maybe "I'd prefer" to replace "if you feel like it").
Jan
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Quoted 10 lines · Jan Beulich
Quoted 8 lines
Quoted 2 lines
Quoted 2 lines · On 07.05.19 at 13:34, <[email protected]> wrote:
xen/common/page_alloc.c +0
-0@@ -214,6 +214,10 @@ custom_param("bootscrub", parse_bootscrub_param);static unsigned long __initdata opt_bootscrub_chunk =MB (128 );size_param ("bootscrub_chunk" , opt_bootscrub_chunk);
Quoted 6 lines
xen/common/page_alloc.c custom_param("bootscrub", parse_bootscrub_param); · line 219
Quoted 3 lines
xen/common/page_alloc.c +3
-0+/* scrub-domheap -> Domheap pages are scrubbed when freed */ +static bool __read_mostly opt_scrub_domheap; +boolean_param ("scrub-domheap" , opt_scrub_domheap);Upon 2nd thought this, btw, would seem to be an excellent candidate for becoming a runtime parameter.
True.
Quoted 15 lines
xen/common/page_alloc.c void free_domheap_pages(struct page_info *pg, unsigned int order) · line 2388
Quoted 11 lines
xen/common/page_alloc.c +3
-2@@ -2378,9 +2382,10 @@ void free_domheap_pages(struct page_info *pg, unsigned int order)/* * Normally we expect a domain to clear pages before freeing them, * if it cares about the secrecy of their contents. However, after -* a domain has died we assume responsibility for erasure. +* a domain has died we assume responsibility for erasure. We do +* scrub regardless if option scrub_domheap is set. */ - scrub = d->is_dying || scrub_debug; + scrub = d->is_dying || scrub_debug || opt_scrub_domheap;Did you consider setting
opt_scrub_domheapwhenscrub_debugis set? This would shorten the (runtime) calculation here by a tiny bit, at the price of doing one more thing once while booting.
Interesting. I have not particularly thought about that. Granted; this would shorten the “scrub” bool calculation. One would probably define a bool ‘always_scrub’ that gets set at boot ‘always_scrub = scrub_debug || opt_scrub_domheap’, and use that new bool in the hunk at hand here. (Having opt_scrub_domheap as a runtime parameter and re-evaluating always_scrub should not be much of a complication either).
In any case, given your response to George earlier, I would rather decouple these improvements from this patch. I would be happy to re-work these improvements at a later point if the community feels strongly about them.
Quoted 4 lines
Jan
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel