From: Rabin Vincent <rabin.vincent@axis.com>
To: Borislav Petkov <bp@suse.de>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] printk: fix printk.devkmsg sysctl
Date: Fri, 27 Jan 2017 16:42:30 +0100 [thread overview]
Message-ID: <20170127154230.GB3799@axis.com> (raw)
In-Reply-To: <20170127150141.5w33ardlqab6rekz@pd.tnic>
On Fri, Jan 27, 2017 at 04:01:41PM +0100, Borislav Petkov wrote:
> On Fri, Jan 27, 2017 at 02:11:46PM +0100, Rabin Vincent wrote:
> > @@ -177,7 +177,7 @@ int devkmsg_sysctl_set_loglvl(struct ctl_table *table, int write,
> > * Do not accept an unknown string OR a known string with
> > * trailing crap...
> > */
> > - if (err < 0 || (err + 1 != *lenp)) {
>
> Grr, that's that damn '\n'
>
> echo off > /proc/sys/kernel/printk_devkmsg
>
> works, of course.
>
> Ok, I don't want to relax the strncmp() above and would still like to
> return the exact length compared.
>
> So please change the check above to allow the following inputs:
>
> <str>
>
> or
>
> <str>\n
>
> I.e., a trailing, *optional*, '\n' is allowed.
proc_dostring() eats the '\n' and stops after that so we never see it or
what comes after, so we need an strlen():
8<----
>From ec7e02cdf5b6c9fb1492670928bb7ea4386ca87d Mon Sep 17 00:00:00 2001
From: Rabin Vincent <rabinv@axis.com>
Date: Fri, 27 Jan 2017 14:03:07 +0100
Subject: [PATCHv2] printk: fix printk.devkmsg sysctl
The comment says that it doesn't want to accept trailing crap but the
code does allow it:
# echo -n offX > /proc/sys/kernel/printk_devkmsg
#
while at the same time it rejects legitimate uses:
# echo -n off > /proc/sys/kernel/printk_devkmsg
-sh: echo: write error: Invalid argument
Fix it.
Before this patch:
# cat /proc/sys/kernel/printk_devkmsg
ratelimit
# echo off > /proc/sys/kernel/printk_devkmsg
# sysctl -w kernel.printk_devkmsg=off
sysctl: short write
# echo -n off > /proc/sys/kernel/printk_devkmsg
-sh: echo: write error: Invalid argument
# echo -n offX > /proc/sys/kernel/printk_devkmsg
#
# printf "off\nX" >/proc/sys/kernel/printk_devkmsg
-sh: printf: write error: Invalid argument
After this patch:
# cat /proc/sys/kernel/printk_devkmsg
ratelimit
# echo off > /proc/sys/kernel/printk_devkmsg
# sysctl -w kernel.printk_devkmsg=off
kernel.printk_devkmsg = off
# echo -n off > /proc/sys/kernel/printk_devkmsg
# echo -n offX > /proc/sys/kernel/printk_devkmsg
-sh: echo: write error: Invalid argument
# printf "off\nX" >/proc/sys/kernel/printk_devkmsg
-sh: printf: write error: Invalid argument
Fixes: 750afe7babd117d ("printk: add kernel parameter to control writes to /dev/kmsg")
Signed-off-by: Rabin Vincent <rabinv@axis.com>
---
kernel/printk/printk.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index 8b26964..935ed71 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -177,7 +177,8 @@ int devkmsg_sysctl_set_loglvl(struct ctl_table *table, int write,
* Do not accept an unknown string OR a known string with
* trailing crap...
*/
- if (err < 0 || (err + 1 != *lenp)) {
+ if (err < 0 || (err != *lenp && err + 1 != *lenp) ||
+ err != strlen(devkmsg_log_str)) {
/* ... and restore old setting. */
devkmsg_log = old;
--
2.1.4
next prev parent reply other threads:[~2017-01-27 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 13:11 [PATCH] printk: fix printk.devkmsg sysctl Rabin Vincent
2017-01-27 15:01 ` Borislav Petkov
2017-01-27 15:42 ` Rabin Vincent [this message]
2017-01-27 18:19 ` Borislav Petkov
2017-01-30 13:38 ` Petr Mladek
2017-01-30 17:03 ` Borislav Petkov
2017-01-30 22:39 ` Borislav Petkov
2017-01-31 13:55 ` Petr Mladek
2017-02-02 4:50 ` Sergey Senozhatsky
2017-01-30 17:31 ` Rabin Vincent
2017-01-30 17:40 ` Borislav Petkov
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=20170127154230.GB3799@axis.com \
--to=rabin.vincent@axis.com \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=linux-kernel@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