mount_setattr.2, openat2.2, landlock.7: wfix
PATCH 1/1 mount_setattr.2, openat2.2, landlock.7: wfix
Fix spelling of "run time", as documented in man-pages(7):
* "run time" in two words when used as a noun
* "run-time" with hyphen when used as an adjective
There is another occurrence in bpf-helpers.7, but that content gets generated from the kernel source and should be fixed there.
--- man2/mount_setattr.2 | 2 +- man2/openat2.2 | 2 +- man7/landlock.7 | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
man2/mount_setattr.2 +1 -1
@@ -862,7 +862,7 @@ may change in the future user-space applications should zero-fill .I struct mount_attr to ensure that recompiling the program with new headers will not result in -spurious errors at runtime. +spurious errors at run time. The simplest way is to use a designated initializer: .PP .in +4n
man2/openat2.2 +1 -1
@@ -545,7 +545,7 @@ may change in the future (with new fields being added when system headers are updated), user-space applications should zero-fill .I struct open_how to ensure that recompiling the program with new headers will not result in -spurious errors at runtime. +spurious errors at run time. The simplest way is to use a designated initializer: .PP
man7/landlock.7 +1 -1
@@ -251,7 +251,7 @@ will stay enforced on all this thread's descendants. This allows creating standalone and modular security policies per application, which will automatically be composed between themselves -according to their runtime parent policies. +according to their run-time parent policies. .\" .SS Ptrace restrictions A sandboxed process has less privileges than a non-sandboxed process and
base-commit: 59e44e4511391a98f531c08aaba17391f3b7075b
Signature · 1 line
2.40.0
Whoops, this was meant to be a "V2" patch, of course...
–Günther
Quoted 60 lines · Günther Noack
Fix spelling of "run time", as documented in man-pages(7):
* "run time" in two words when used as a noun
* "run-time" with hyphen when used as an adjectiveThere is another occurrence in bpf-helpers.7, but that content gets generated from the kernel source and should be fixed there.
Signed-off-by Günther Noack <[email protected]>--- man2/mount_setattr.2 | 2 +- man2/openat2.2 | 2 +- man7/landlock.7 | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)man2/mount_setattr.2 +1
-1@@ -862,7 +862,7 @@ may change in the future user-space applications should zero-fill .I struct mount_attr to ensure that recompiling the program with new headers will not result in -spurious errors at runtime. +spurious errors at run time. The simplest way is to use a designated initializer: .PP .in +4nman2/openat2.2 +1
-1@@ -545,7 +545,7 @@ may change in the future (with new fields being added when system headers are updated), user-space applications should zero-fill .I struct open_how to ensure that recompiling the program with new headers will not result in -spurious errors at runtime. +spurious errors at run time. The simplest way is to use a designated initializer: .PPman7/landlock.7 +1
-1@@ -251,7 +251,7 @@ will stay enforced on all this thread's descendants. This allows creating standalone and modular security policies per application, which will automatically be composed between themselves -according to their runtime parent policies. +according to their run-time parent policies. .\" .SS Ptrace restrictions A sandboxed process has less privileges than a non-sandboxed process andbase-commit:
59e44e4511391a98f531c08aaba17391f3b7075bSignature · 1 line
2.40.0
Hi!
Quoted 10 lines · Günther Noack
Fix spelling of "run time", as documented in man-pages(7):
* "run time" in two words when used as a noun
* "run-time" with hyphen when used as an adjectiveThere is another occurrence in bpf-helpers.7, but that content gets generated from the kernel source and should be fixed there.
Signed-off-by Günther Noack <[email protected]>
Patch applied, with minor tweaks to the commit log:
man*/: wfix
Fix spelling of "run time", as documented in man-pages(7):
- "run time" in two words when used as a noun
- "run-time" with hyphen when used as an adjective
There is another occurrence in bpf-helpers.7, but that content gets generated from the kernel source and should be fixed there.
Cheers!
Alex
Quoted 47 lines
--- man2/mount_setattr.2 | 2 +- man2/openat2.2 | 2 +- man7/landlock.7 | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)man2/mount_setattr.2 +1
-1@@ -862,7 +862,7 @@ may change in the future user-space applications should zero-fill .I struct mount_attr to ensure that recompiling the program with new headers will not result in -spurious errors at runtime. +spurious errors at run time. The simplest way is to use a designated initializer: .PP .in +4nman2/openat2.2 +1
-1@@ -545,7 +545,7 @@ may change in the future (with new fields being added when system headers are updated), user-space applications should zero-fill .I struct open_how to ensure that recompiling the program with new headers will not result in -spurious errors at runtime. +spurious errors at run time. The simplest way is to use a designated initializer: .PPman7/landlock.7 +1
-1@@ -251,7 +251,7 @@ will stay enforced on all this thread's descendants. This allows creating standalone and modular security policies per application, which will automatically be composed between themselves -according to their runtime parent policies. +according to their run-time parent policies. .\" .SS Ptrace restrictions A sandboxed process has less privileges than a non-sandboxed process andbase-commit:
59e44e4511391a98f531c08aaba17391f3b7075b
Signature · 2 lines
<http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5