From: "Petr Mládek" <pmladek@suse.cz>
To: Alex Elder <elder@linaro.org>
Cc: akpm@linux-foundation.org, ak@linux.intel.com, bp@suse.de,
jack@suse.cz, john.stultz@linaro.org, rostedt@goodmis.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] printk: miscellaneous cleanups
Date: Wed, 9 Jul 2014 18:29:35 +0200 [thread overview]
Message-ID: <20140709162935.GB26508@pathway.suse.cz> (raw)
In-Reply-To: <1404911056-29064-5-git-send-email-elder@linaro.org>
Sending once again as a correct reply. I am sorry for the
confusion. I think that it is high time for me to go home and sleep :-)
On Wed 2014-07-09 08:04:16, Alex Elder wrote:
> This patch contains some small cleanups to kernel/printk/printk.c.
> None of them should cause any change in behavior.
> - When CONFIG_PRINTK is defined, parenthesize the value of LOG_LINE_MAX.
> - When CONFIG_PRINTK is *not* defined, there is an extra LOG_LINE_MAX
> definition; delete it.
> - Pull an assignment out of a conditional expression in console_setup().
> - Use isdigit() in console_setup() rather than open coding it.
> - In update_console_cmdline(), drop a NUL-termination assignment;
> the strlcpy() call that precedes it guarantees it's not needed.
> - Simplify some logic in printk_timed_ratelimit().
>
> Signed-off-by: Alex Elder <elder@linaro.org>
> ---
> kernel/printk/printk.c | 26 +++++++++++++-------------
> 1 file changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index 6f75e8a..909029e 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -45,6 +45,7 @@
> #include <linux/poll.h>
> #include <linux/irq_work.h>
> #include <linux/utsname.h>
> +#include <linux/ctype.h>
>
> #include <asm/uaccess.h>
>
> @@ -257,7 +258,7 @@ static u64 clear_seq;
> static u32 clear_idx;
>
> #define PREFIX_MAX 32
> -#define LOG_LINE_MAX 1024 - PREFIX_MAX
> +#define LOG_LINE_MAX (1024 - PREFIX_MAX)
>
> /* record buffer */
> #if defined(CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS)
> @@ -1794,7 +1795,7 @@ EXPORT_SYMBOL(printk);
>
> #define LOG_LINE_MAX 0
> #define PREFIX_MAX 0
> -#define LOG_LINE_MAX 0
> +
> static u64 syslog_seq;
> static u32 syslog_idx;
> static u64 console_seq;
> @@ -1895,7 +1896,8 @@ static int __init console_setup(char *str)
> strncpy(buf, str, sizeof(buf) - 1);
> }
> buf[sizeof(buf) - 1] = 0;
> - if ((options = strchr(str, ',')) != NULL)
> + options = strchr(str, ',');
> + if (options)
> *(options++) = 0;
> #ifdef __sparc__
> if (!strcmp(str, "ttya"))
> @@ -1904,7 +1906,7 @@ static int __init console_setup(char *str)
> strcpy(buf, "ttyS1");
> #endif
> for (s = buf; *s; s++)
> - if ((*s >= '0' && *s <= '9') || *s == ',')
> + if (isdigit(*s) || *s == ',')
> break;
> idx = simple_strtoul(s, NULL, 10);
> *s = 0;
> @@ -1943,7 +1945,6 @@ int update_console_cmdline(char *name, int idx, char *name_new, int idx_new, cha
> i++, c++)
> if (strcmp(c->name, name) == 0 && c->index == idx) {
> strlcpy(c->name, name_new, sizeof(c->name));
> - c->name[sizeof(c->name) - 1] = 0;
> c->options = options;
> c->index = idx_new;
> return i;
> @@ -2611,14 +2612,13 @@ EXPORT_SYMBOL(__printk_ratelimit);
> bool printk_timed_ratelimit(unsigned long *caller_jiffies,
> unsigned int interval_msecs)
> {
> - if (*caller_jiffies == 0
> - || !time_in_range(jiffies, *caller_jiffies,
> - *caller_jiffies
> - + msecs_to_jiffies(interval_msecs))) {
> - *caller_jiffies = jiffies;
> - return true;
> - }
> - return false;
> + unsigned long elapsed = jiffies - *caller_jiffies;
I wondered if the deduction might be negative. Well, it should not be
if none manipulates *caller_jiffies in a strange way. If it happens,
the following condition will most likely fail and *caller_jiffies will
get reset to jiffies. It looks reasonable to me.
Reviewed-by: Petr Mladek <pmladek@suse.cz>
> + if (*caller_jiffies && elapsed <= msecs_to_jiffies(interval_msecs))
> + return false;
> +
> + *caller_jiffies = jiffies;
> + return true;
> }
> EXPORT_SYMBOL(printk_timed_ratelimit);
Best Regards,
Petr
next prev parent reply other threads:[~2014-07-09 16:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 13:04 [PATCH 0/4] printk: some minor fixups Alex Elder
2014-07-09 13:04 ` [PATCH 1/4] printk: rename DEFAULT_MESSAGE_LOGLEVEL Alex Elder
2014-07-09 15:00 ` Borislav Petkov
2014-07-09 15:10 ` Alex Elder
2014-07-09 15:13 ` Borislav Petkov
2014-07-09 15:14 ` Alex Elder
2014-07-09 15:17 ` Borislav Petkov
2014-07-09 13:04 ` [PATCH 2/4] printk: fix some comments Alex Elder
2014-07-09 15:53 ` Petr Mládek
2014-07-09 13:04 ` [PATCH 3/4] printk: use a clever macro Alex Elder
2014-07-09 15:05 ` Borislav Petkov
2014-07-09 16:19 ` Petr Mládek
2014-07-09 16:24 ` Borislav Petkov
2014-07-09 16:32 ` Petr Mládek
2014-07-09 16:40 ` Borislav Petkov
2014-07-09 17:58 ` Geert Uytterhoeven
2014-07-09 18:15 ` Alex Elder
2014-07-09 13:04 ` [PATCH 4/4] printk: miscellaneous cleanups Alex Elder
2014-07-09 16:29 ` Petr Mládek [this message]
2014-07-09 16:45 ` Alex Elder
2014-07-09 16:03 ` Alex Elder
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=20140709162935.GB26508@pathway.suse.cz \
--to=pmladek@suse.cz \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=elder@linaro.org \
--cc=jack@suse.cz \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®