From: Rusty Russell <rusty@rustcorp.com.au>
To: Chen Gang <gang.chen@asianux.com>
Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel/module.c: use scnprintf() instead of sprintf()
Date: Tue, 20 Aug 2013 15:34:42 +0930 [thread overview]
Message-ID: <87vc30gao5.fsf@rustcorp.com.au> (raw)
In-Reply-To: <5212DEC3.9070007@asianux.com>
Chen Gang <gang.chen@asianux.com> writes:
> For some strings, they are permitted to be larger than PAGE_SIZE, so
> need use scnprintf() instead of sprintf(), or it will cause issue.
>
> One case is:
>
> if a module version is crazy defined (length more than PAGE_SIZE),
> 'modinfo' command is still OK (print full contents),
> but for "cat /sys/modules/'modname'/version", will cause issue in kernel.
Applied!
Thanks,
Rusty.
>
> Signed-off-by: Chen Gang <gang.chen@asianux.com>
> ---
> kernel/module.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/module.c b/kernel/module.c
> index 2069158..0618e63 100644
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -603,7 +603,7 @@ static void setup_modinfo_##field(struct module *mod, const char *s) \
> static ssize_t show_modinfo_##field(struct module_attribute *mattr, \
> struct module_kobject *mk, char *buffer) \
> { \
> - return sprintf(buffer, "%s\n", mk->mod->field); \
> + return scnprintf(buffer, PAGE_SIZE, "%s\n", mk->mod->field); \
> } \
> static int modinfo_##field##_exists(struct module *mod) \
> { \
> --
> 1.7.7.6
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2013-08-21 1:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 3:13 [PATCH] kernel/module.c: use scnprintf() instead of sprintf() Chen Gang
2013-08-20 6:04 ` Rusty Russell [this message]
2013-08-21 2:03 ` Chen Gang
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=87vc30gao5.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=gang.chen@asianux.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