From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Petr Mladek <pmladek@suse.com>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH] printk: drop redundant devkmsg_log_str memsets
Date: Sat, 20 Jan 2018 15:05:29 +0900 [thread overview]
Message-ID: <20180120060529.GA8371@jagdpanzerIV> (raw)
In-Reply-To: <20180119091707.0a15a24d@gandalf.local.home>
On (01/19/18 09:17), Steven Rostedt wrote:
> Yep, and even the sysctl checks for the terminating nul string, so
> there's no leaks of any kind.
>
> Tested by adding: printk.devkmsg=on and running:
>
> $ hexdump -C /proc/sys/kernel/printk_devkmsg
> 00000000 6f 6e 0a |on.|
> 00000003
>
>
> Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
thanks.
-ss
next prev parent reply other threads:[~2018-01-20 6:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 4:39 [PATCH] printk: drop redundant devkmsg_log_str memsets Sergey Senozhatsky
2018-01-19 14:17 ` Steven Rostedt
2018-01-20 6:05 ` Sergey Senozhatsky [this message]
2018-01-22 9:54 ` Petr Mladek
2018-01-22 9:59 ` Sergey Senozhatsky
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=20180120060529.GA8371@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@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;
as well as URLs for NNTP newsgroup(s).