public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: linux-block@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>,
	kernel-team@fb.com, Jordan Glover <Golden_Miller83@protonmail.ch>
Subject: Re: [PATCH] kyber: fix wrong strlcpy() size in trace_kyber_latency()
Date: Sun, 11 Nov 2018 10:13:45 -0800	[thread overview]
Message-ID: <20181111181345.GB24956@vader> (raw)
In-Reply-To: <8233c3aac03494d50bf463787661edc523292ae4.1541957005.git.osandov@fb.com>

On Sun, Nov 11, 2018 at 09:25:27AM -0800, Omar Sandoval wrote:
> From: Omar Sandoval <osandov@fb.com>
> 
> When copying to the latency type, we should be passing LATENCY_TYPE_LEN,
> not DOMAIN_LEN. This isn't a problem in practice because we only pass
> "total" or "I/O", but let's fix it.

Oh, I forgot

Fixes: 6c3b7af1c975 ("kyber: add tracepoints")

> Reported-by: Jordan Glover <Golden_Miller83@protonmail.ch>
> Signed-off-by: Omar Sandoval <osandov@fb.com>
> ---
>  include/trace/events/kyber.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/trace/events/kyber.h b/include/trace/events/kyber.h
> index a9834c37ac40..7aaa298375ad 100644
> --- a/include/trace/events/kyber.h
> +++ b/include/trace/events/kyber.h
> @@ -32,7 +32,7 @@ TRACE_EVENT(kyber_latency,
>  	TP_fast_assign(
>  		__entry->dev		= disk_devt(dev_to_disk(kobj_to_dev(q->kobj.parent)));
>  		strlcpy(__entry->domain, domain, DOMAIN_LEN);
> -		strlcpy(__entry->type, type, DOMAIN_LEN);
> +		strlcpy(__entry->type, type, LATENCY_TYPE_LEN);
>  		__entry->percentile	= percentile;
>  		__entry->numerator	= numerator;
>  		__entry->denominator	= denominator;
> -- 
> 2.19.1
> 

  reply	other threads:[~2018-11-11 18:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-11 17:25 [PATCH] kyber: fix wrong strlcpy() size in trace_kyber_latency() Omar Sandoval
2018-11-11 18:13 ` Omar Sandoval [this message]
2018-11-11 19:11 ` Bart Van Assche

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=20181111181345.GB24956@vader \
    --to=osandov@osandov.com \
    --cc=Golden_Miller83@protonmail.ch \
    --cc=axboe@kernel.dk \
    --cc=kernel-team@fb.com \
    --cc=linux-block@vger.kernel.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