From: Seth Arnold <seth.arnold@canonical.com>
To: Kees Cook <keescook@chromium.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs_parse: Remove pr_notice() about each validation
Date: Wed, 11 Mar 2020 18:03:26 +0000 [thread overview]
Message-ID: <20200311180326.GA2007141@millbarge> (raw)
In-Reply-To: <202003061617.A8835CAAF@keescook>
On Fri, Mar 06, 2020 at 04:20:02PM -0800, Kees Cook wrote:
> This notice fills my boot logs with scary-looking asterisks but doesn't
> really tell me anything. Let's just remove it; validation errors
> are already reported separately, so this is just a redundant list of
> filesystems.
>
> $ dmesg | grep VALIDATE
> [ 0.306256] *** VALIDATE tmpfs ***
> [ 0.307422] *** VALIDATE proc ***
> [ 0.308355] *** VALIDATE cgroup ***
> [ 0.308741] *** VALIDATE cgroup2 ***
> [ 0.813256] *** VALIDATE bpf ***
> [ 0.815272] *** VALIDATE ramfs ***
> [ 0.815665] *** VALIDATE hugetlbfs ***
> [ 0.876970] *** VALIDATE nfs ***
> [ 0.877383] *** VALIDATE nfs4 ***
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
Excellent, these messages haven't been useful in helping users diagnose
problems and they look quite noisy considering how mundane they are.
Reviewed-by: Seth Arnold <seth.arnold@canonical.com>
Thanks
> ---
> fs/fs_parser.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/fs/fs_parser.c b/fs/fs_parser.c
> index 7e6fb43f9541..ab53e42a874a 100644
> --- a/fs/fs_parser.c
> +++ b/fs/fs_parser.c
> @@ -368,8 +368,6 @@ bool fs_validate_description(const char *name,
> const struct fs_parameter_spec *param, *p2;
> bool good = true;
>
> - pr_notice("*** VALIDATE %s ***\n", name);
> -
> for (param = desc; param->name; param++) {
> /* Check for duplicate parameter names */
> for (p2 = desc; p2 < param; p2++) {
> --
> 2.20.1
>
>
> --
> Kees Cook
prev parent reply other threads:[~2020-03-11 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 0:20 [PATCH] fs_parse: Remove pr_notice() about each validation Kees Cook
2020-03-11 17:20 ` Kees Cook
2020-03-11 18:03 ` Seth Arnold [this message]
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=20200311180326.GA2007141@millbarge \
--to=seth.arnold@canonical.com \
--cc=akpm@linux-foundation.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).