mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Salvatore Mesoraca <s.mesoraca16@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	kernel-hardening@lists.openwall.com,
	Ingo Molnar <mingo@redhat.com>, Kees Cook <keescook@chromium.org>
Subject: Re: [v2] ftrace: drop a VLA in module_exists()
Date: Fri, 30 Mar 2018 10:34:11 -0400	[thread overview]
Message-ID: <20180330103411.5ed25f43@gandalf.local.home> (raw)
In-Reply-To: <1522399988-8815-1-git-send-email-s.mesoraca16@gmail.com>

On Fri, 30 Mar 2018 10:53:08 +0200
Salvatore Mesoraca <s.mesoraca16@gmail.com> wrote:

Couple of things. First, "PATCH" was dropped from the subject. If my
inbox was busy today, I probably would have missed this email.

> Avoid a VLA[1] by using a real constant expression instead of a variable.
> The compiler should be able to optimize the original code and avoid using
> an actual VLA. Anyway this change is useful because it will avoid a false
> positive with -Wvla, it might also help the compiler generating better
> code.
> 
> [1] https://lkml.org/lkml/2018/3/7/621

Second, do not use lkml.org, use http://lkml.kernel.org/r/<messageid>

Search for "Link:" tags in git log to see examples.

Other than that, the patch looks fine to me and I can pull it for the
next merge window.

-- Steve

> 
> Signed-off-by: Salvatore Mesoraca <s.mesoraca16@gmail.com>
> ---
>  kernel/trace/ftrace.c | 7 +++----
>  1 file changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
> index eac9ce2..16bbf06 100644
> --- a/kernel/trace/ftrace.c
> +++ b/kernel/trace/ftrace.c
> @@ -3902,14 +3902,13 @@ static bool module_exists(const char *module)
>  {
>  	/* All modules have the symbol __this_module */
>  	const char this_mod[] = "__this_module";
> -	const int modname_size = MAX_PARAM_PREFIX_LEN + sizeof(this_mod) + 1;
> -	char modname[modname_size + 1];
> +	char modname[MAX_PARAM_PREFIX_LEN + sizeof(this_mod) + 2];
>  	unsigned long val;
>  	int n;
>  
> -	n = snprintf(modname, modname_size + 1, "%s:%s", module, this_mod);
> +	n = snprintf(modname, sizeof(modname), "%s:%s", module, this_mod);
>  
> -	if (n > modname_size)
> +	if (n > sizeof(modname) - 1)
>  		return false;
>  
>  	val = module_kallsyms_lookup_name(modname);

  reply	other threads:[~2018-03-30 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-30  8:53 Salvatore Mesoraca
2018-03-30 14:34 ` Steven Rostedt [this message]
2018-03-31  9:55   ` Salvatore Mesoraca

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=20180330103411.5ed25f43@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=s.mesoraca16@gmail.com \
    /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

all inboxes | Powered by JetHome®