Commit 751d5b27 authored by Andrew Klychkov's avatar Andrew Klychkov Committed by Jonathan Corbet
Browse files

Documentation: fix multiple typos found in the admin-guide subdirectory 



Fix thirty five typos in dm-integrity.rst, dm-raid.rst, dm-zoned.rst,
verity.rst, writecache.rst, tsx_async_abort.rst, md.rst, bttv.rst,
dvb_references.rst, frontend-cardlist.rst, gspca-cardlist.rst, ipu3.rst,
remote-controller.rst, mm/index.rst, numaperf.rst, userfaultfd.rst,
module-signing.rst, imx-ddr.rst, intel-speed-select.rst,
intel_pstate.rst, ramoops.rst, abi.rst, kernel.rst, vm.rst

Signed-off-by: default avatarAndrew Klychkov <andrew.a.klychkov@gmail.com>
Link: https://lore.kernel.org/r/20201204072848.GA49895@spblnx124.lan


Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent b2105aa2

Documentation/admin-guide/device-mapper/dm-integrity.rst

+2 −2
Original line number Diff line number Diff line
@@ -117,7 +117,7 @@ journal_watermark:number 


commit_time:number

	Commit time in milliseconds. When this time passes, the journal is

	written. The journal is also written immediatelly if the FLUSH

	written. The journal is also written immediately if the FLUSH

	request is received.



internal_hash:algorithm(:key)	(the key is optional)
@@ -147,7 +147,7 @@ journal_crypt:algorithm(:key) (the key is optional) 
	"salsa20" or "ctr(aes)").



	The journal contains history of last writes to the block device,

	an attacker reading the journal could see the last sector nubmers

	an attacker reading the journal could see the last sector numbers

	that were written. From the sector numbers, the attacker can infer

	the size of files that were written. To protect against this

	situation, you can encrypt the journal.

Documentation/admin-guide/device-mapper/dm-raid.rst

+1 −1
Original line number Diff line number Diff line
@@ -418,6 +418,6 @@ Version History 
	specific devices are requested via rebuild.  Fix RAID leg

	rebuild errors.

 1.15.0 Fix size extensions not being synchronized in case of new MD bitmap

        pages allocated;  also fix those not occuring after previous reductions

        pages allocated;  also fix those not occurring after previous reductions

 1.15.1 Fix argument count and arguments for rebuild/write_mostly/journal_(dev|mode)

        on the status line.

Documentation/admin-guide/device-mapper/dm-zoned.rst

+3 −3
Original line number Diff line number Diff line
@@ -24,7 +24,7 @@ The dm-zoned implementation is simple and minimizes system overhead (CPU 
and memory usage as well as storage capacity loss). For a 10TB

host-managed disk with 256 MB zones, dm-zoned memory usage per disk

instance is at most 4.5 MB and as little as 5 zones will be used

internally for storing metadata and performaing reclaim operations.

internally for storing metadata and performing reclaim operations.



dm-zoned target devices are formatted and checked using the dmzadm

utility available at:
@@ -102,7 +102,7 @@ the buffer zone assigned. If the accessed chunk has no mapping, or the 
accessed blocks are invalid, the read buffer is zeroed and the read

operation terminated.



After some time, the limited number of convnetional zones available may

After some time, the limited number of conventional zones available may

be exhausted (all used to map chunks or buffer sequential zones) and

unaligned writes to unbuffered chunks become impossible. To avoid this

situation, a reclaim process regularly scans used conventional zones and
@@ -158,7 +158,7 @@ Ex:: 
	dmzadm --format /dev/sdxx /dev/sdyy





Fomatted device(s) can be started with the dmzadm utility, too.:

Formatted device(s) can be started with the dmzadm utility, too.:



Ex::

Documentation/admin-guide/device-mapper/verity.rst

+1 −1
Original line number Diff line number Diff line
@@ -69,7 +69,7 @@ Construction Parameters 


<#opt_params>

    Number of optional parameters. If there are no optional parameters,

    the optional paramaters section can be skipped or #opt_params can be zero.

    the optional parameters section can be skipped or #opt_params can be zero.

    Otherwise #opt_params is the number of following arguments.



    Example of optional parameters section:

Documentation/admin-guide/device-mapper/writecache.rst

+2 −2
Original line number Diff line number Diff line
@@ -37,10 +37,10 @@ Constructor parameters: 
	autocommit_blocks n	(default: 64 for pmem, 65536 for ssd)

		when the application writes this amount of blocks without

		issuing the FLUSH request, the blocks are automatically

		commited

		committed

	autocommit_time ms	(default: 1000)

		autocommit time in milliseconds. The data is automatically

		commited if this time passes and no FLUSH request is

		committed if this time passes and no FLUSH request is

		received

	fua			(by default on)

		applicable only to persistent memory - use the FUA flag

CRA Git | Maintained and supported by SUSTech CRA and CCSE