Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(3035)

Unified Diff: base/allocator/partition_allocator/PartitionAlloc.md

Issue 2689103002: Fix partition_alloc unit tests. (Closed)
Patch Set: Created 3 years, 10 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: base/allocator/partition_allocator/PartitionAlloc.md
diff --git a/base/allocator/partition_allocator/PartitionAlloc.md b/base/allocator/partition_allocator/PartitionAlloc.md
index dbcc0061c2b87da0519bda34467f691b63610ac5..e04016b22bc01791b1958c8b6c0beb3a7eb32330 100644
--- a/base/allocator/partition_allocator/PartitionAlloc.md
+++ b/base/allocator/partition_allocator/PartitionAlloc.md
@@ -2,7 +2,7 @@
This document explains a high-level design of PartitionAlloc.
If you're interested in its in-depth implementation, see comments
-in PartitionAlloc.h.
+in partition_alloc.h.
[TOC]
@@ -73,7 +73,7 @@ the physical memory is returned to the system but the address space
remains reserved. The address space may be reused later only for the partition.
Remember that PartitionAlloc puts LayoutObjects into a dedicated partition.
This is because LayoutObjects are likely to be a source of use-after-free.
-Simiarly, PartitionAlloc puts Strings, Vectors etc into the Buffer partition
+Similarly, PartitionAlloc puts Strings, Vectors etc into the Buffer partition
because the length and/or contents may be exploited by user scripts.
This means that PartitionAlloc greedily uses virtual address spaces in favor of
security hardening.

Powered by Google App Engine
This is Rietveld 408576698