lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 29 Mar 2021 10:42:41 +0530
From:   Bhaskar Chowdhury <unixbhaskar@...il.com>
To:     corbet@....net, linux-doc@...r.kernel.org
Cc:     Bhaskar Chowdhury <unixbhaskar@...il.com>, rdunlap@...radead.org,
        linux-kernel@...r.kernel.org
Subject: [PATCH 05/23] vm: unevictable-lru.rst: Fix a typo

s/mmaped/mapped/

Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>
---
 Documentation/vm/unevictable-lru.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/vm/unevictable-lru.rst b/Documentation/vm/unevictable-lru.rst
index 0e1490524f53..74e7d5ded114 100644
--- a/Documentation/vm/unevictable-lru.rst
+++ b/Documentation/vm/unevictable-lru.rst
@@ -467,7 +467,7 @@ In addition the mlock()/mlockall() system calls, an application can request
 that a region of memory be mlocked supplying the MAP_LOCKED flag to the mmap()
 call. There is one important and subtle difference here, though. mmap() + mlock()
 will fail if the range cannot be faulted in (e.g. because mm_populate fails)
-and returns with ENOMEM while mmap(MAP_LOCKED) will not fail. The mmaped
+and returns with ENOMEM while mmap(MAP_LOCKED) will not fail. The mapped
 area will still have properties of the locked area - aka. pages will not get
 swapped out - but major page faults to fault memory in might still happen.

--
2.26.3

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ