From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: zhe.he@windriver.com
Cc: pmladek@suse.com, sergey.senozhatsky@gmail.com,
rostedt@goodmis.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] printk: Fix panic caused by passing log_buf_len to command line
Date: Sat, 29 Sep 2018 17:26:19 +0900 [thread overview]
Message-ID: <20180929082619.GA582@tigerII.localdomain> (raw)
In-Reply-To: <1538145961-52724-1-git-send-email-zhe.he@windriver.com>
On (09/28/18 22:46), zhe.he@windriver.com wrote:
> This patch adds a check to prevent the panic and a check to report if someone is
> setting it over 4G.
OK, He Zhe, you are almost there.
Let's do the series the following way:
- four patches
- each change goes into a separate patch
- the first two patches Cc stable
patch #0 Cc stable
---
unsigned int size;
if (!str)
return -EINVAL;
size = memparse(str, &str);
---
patch #1 Cc stable
---
len = sprintf(text,
"** %llu printk messages dropped **\n",
log_first_seq - console_seq);
---
=====================================================================
patch #2
---
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
---
patch #3
---
if (size > UINT_MAX) {
size = UINT_MAX;
pr_err("log_buf over 4G is not supported.\n");
}
...
---
-ss
next prev parent reply other threads:[~2018-09-29 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 14:46 [PATCH v3 1/2] printk: Fix panic caused by passing log_buf_len to command line zhe.he
2018-09-28 14:46 ` [PATCH v2 2/2] printk: Add KBUILD_MODNAME and correct wrong casting zhe.he
2018-09-29 8:26 ` Sergey Senozhatsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-22 15:40 [PATCH v3 1/2] printk: Fix panic caused by passing log_buf_len to command line zhe.he
2018-09-22 16:19 ` Steven Rostedt
2018-09-23 6:51 ` He Zhe
2018-09-24 13:11 ` Steven Rostedt
2018-09-25 11:25 ` Petr Mladek
2018-09-25 11:38 ` Sergey Senozhatsky
2018-09-25 11:55 ` Petr Mladek
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=20180929082619.GA582@tigerII.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=zhe.he@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.