From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Shuah Khan <skhan@linuxfoundation.org>, corbet@lwn.net
Cc: kstewart@linuxfoundation.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: add system-state document to admin-guide
Date: Wed, 22 Mar 2023 16:29:23 +0700 [thread overview]
Message-ID: <ZBrKcwoFMAhmIn1f@debian.me> (raw)
In-Reply-To: <20230321231816.31131-1-skhan@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
On Tue, Mar 21, 2023 at 05:18:16PM -0600, Shuah Khan wrote:
> +scripts/checksyscalls.sh can be used to check if current architecture is
> +missing any function calls compared to i386.
i386 is the reference architecture for comparing syscalls, right?
> +This scripts parses Documentation/features to find the support status
> +information. It can be used to validate the contents of the files under
> +Documentation/features or simply list.::
"... to validate contents of Documentation/features files or simply list
them::"
> +Let's do one last sanity check on the system to see if the following two
> +command outputs match. If they don't examine your system closely. kernel
> +rootkits install their own ps, find, etc. utilities to mask their activity.
> +The outputs match on my system. Do they on yours?
> +
> +ps ax | wc -l
> +ls -d /proc/* | grep [0-9]|wc -l
The shell snippet above should be in a code block for consistency
with other snippets.
> +Linux kernel supports several hardening options to make system secure.
> +kconfig-hardened-check tool sanity checks kernel configuration for
> +security. You can checkout the latest::
"... If you don't have the tool handy, you can clone the repository::"
> + * https://docs.kernel.org/trace/index.html
Shouldn't the last ref be internal link (Documentation/trace/index.rst)?
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-03-22 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 23:18 [PATCH] docs: add system-state document to admin-guide Shuah Khan
2023-03-22 9:29 ` Bagas Sanjaya [this message]
2023-03-22 14:37 ` Shuah Khan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZBrKcwoFMAhmIn1f@debian.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=kstewart@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).