From: Andrew Morton <akpm@linux-foundation.org>
To: Ameen Ali <ameenali023@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ameen Ali <Ameenali023@gmail.com>
Subject: Re: [PATCH 2/2] staging: replace simple_strtoul with kstroul
Date: Fri, 20 Feb 2015 14:32:05 -0800 [thread overview]
Message-ID: <20150220143205.a7d70f9bfc422995ba8fb909@linux-foundation.org> (raw)
In-Reply-To: <1424384037-4081-1-git-send-email-ameenali023@gmail.com>
On Fri, 20 Feb 2015 00:13:57 +0200 Ameen Ali <ameenali023@gmail.com> wrote:
> Subject: [PATCH 2/2] staging: replace simple_strtoul with kstroul
This isn't a staging patch.
s/kstroul/kstrtoul/
> Date: Fri, 20 Feb 2015 00:13:57 +0200
> X-Mailer: git-send-email 2.1.0
>
> Replacing obsolete simple_stroul with kstroul
s/kstroul/kstrtoul/
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -518,7 +518,7 @@ struct devkmsg_user {
> static ssize_t devkmsg_write(struct kiocb *iocb, struct iov_iter *from)
> {
> char *buf, *line;
> - int i;
> + unsigned long int i;
It would be better to move this definition so it is local to the `if'
loop where it is used. And to give it a meaningful name - using `i' is lame.
> int level = default_message_loglevel;
> int facility = 1; /* LOG_USER */
> size_t len = iocb->ki_nbytes;
> @@ -549,7 +549,7 @@ static ssize_t devkmsg_write(struct kiocb *iocb, struct iov_iter *from)
> if (line[0] == '<') {
> char *endp = NULL;
>
> - i = simple_strtoul(line+1, &endp, 10);
> + i = kstrtoul(line+1,10, &endp);
> if (endp && endp[0] == '>') {
> level = i & 7;
> if (i >> 3)
The interfaces are different - kstrtoul() can return a negative errno.
afaict we'll only have issues if someone tried to print "<>..", but
this string is coming from userspace so we must be very paranoid.
prev parent reply other threads:[~2015-02-20 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 22:13 Ameen Ali
2015-02-20 22:32 ` Andrew Morton [this message]
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=20150220143205.a7d70f9bfc422995ba8fb909@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ameenali023@gmail.com \
--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
all inboxes | Powered by JetHome®