From: Rusty Russell <rusty@rustcorp.com.au>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] module: Remove double spaces in module verification taint message
Date: Tue, 23 Dec 2014 15:11:26 +1030 [thread overview]
Message-ID: <8761d3t1u1.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1419269144-91285-1-git-send-email-marcel@holtmann.org>
Marcel Holtmann <marcel@holtmann.org> writes:
> The warning message when loading modules with a wrong signature has
> two spaces in it:
>
> "module verification failed: signature and/or required key missing"
>
> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Rather trivial, but I've applied it.
Thanks,
Rusty.
> ---
> kernel/module.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/module.c b/kernel/module.c
> index e52a8739361a..57f786bae64d 100644
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -3242,7 +3242,7 @@ static int load_module(struct load_info *info, const char __user *uargs,
> mod->sig_ok = info->sig_ok;
> if (!mod->sig_ok) {
> pr_notice_once("%s: module verification failed: signature "
> - "and/or required key missing - tainting "
> + "and/or required key missing - tainting "
> "kernel\n", mod->name);
> add_taint_module(mod, TAINT_UNSIGNED_MODULE, LOCKDEP_STILL_OK);
> }
> --
> 2.1.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2014-12-23 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 17:25 [PATCH] module: Remove double spaces in module verification taint message Marcel Holtmann
2014-12-23 4:41 ` Rusty Russell [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=8761d3t1u1.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.