From: Ingo Molnar <mingo@kernel.org>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] panic: setup panic_timeout early
Date: Fri, 15 Nov 2013 12:27:35 +0100 [thread overview]
Message-ID: <20131115112735.GA19004@gmail.com> (raw)
In-Reply-To: <CAMP44s17p0ZpFx0Y2E_K7Oq9c4tk2J+9uXRWDYChAD-yM-4JjQ@mail.gmail.com>
* Felipe Contreras <felipe.contreras@gmail.com> wrote:
> On Tue, Nov 12, 2013 at 6:03 PM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> >> +static int __init set_panic_timeout(char *val)
> >> +{
> >> + long timeout;
> >> + int ret;
> >> +
> >> + ret = kstrtol(val, 0, &timeout);
> >> + if (ret < 0)
> >> + return ret;
> >> +
> >> + panic_timeout = timeout;
> >> + return 0;
> >> +}
> >
> > I think the type of the 'timeout' local variable should match the type of
> > 'panic_timeout' (which is 'int', not 'long').
>
> So you would rather have this?
>
> kstrtol(val, 0, (long *)&timeout);
>
> Couldn't that potentially write the value beyond the memory
> allocated to 'timeout'?
No, casting that to 'long *' is actively wrong, I'd use a
string -> integer conversion method that deals with ints,
not longs, such as kstrtoint().
Thanks,
Ingo
prev parent reply other threads:[~2013-11-15 11:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 14:40 [PATCH v2] panic: setup panic_timeout early Felipe Contreras
2013-11-13 0:03 ` Ingo Molnar
2013-11-14 11:16 ` Felipe Contreras
2013-11-14 17:42 ` Levente Kurusa
[not found] ` <52853fe6b0fd9_bf6d31e7c1a@nysa.notmuch>
2013-11-14 22:32 ` Felipe Contreras
2013-11-15 13:12 ` Levente Kurusa
2013-11-15 19:33 ` Felipe Contreras
2013-11-15 19:55 ` Linus Torvalds
2013-11-15 20:10 ` Felipe Contreras
2013-11-15 20:15 ` Linus Torvalds
2013-11-15 20:45 ` Felipe Contreras
2013-11-16 17:45 ` Ingo Molnar
2013-11-16 18:46 ` Felipe Contreras
2013-11-16 20:15 ` Levente Kurusa
2013-11-16 20:24 ` Levente Kurusa
2013-11-15 11:27 ` Ingo Molnar [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=20131115112735.GA19004@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=felipe.contreras@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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