From: Rusty Russell <rusty@rustcorp.com.au>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] modpost: abort if a module symbol is too long
Date: Sat, 08 Aug 2015 15:17:35 +0930 [thread overview]
Message-ID: <87io8qbabs.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1438930547-32663-1-git-send-email-tiwai@suse.de>
Takashi Iwai <tiwai@suse.de> writes:
> Module symbols have a limited length, but currently the build system
> allows the build finishing even if the driver code contains a too long
> symbol name, which eventually overflows the modversion_info[] item.
> The compiler may catch at compiling *.mod.c like
> CC xxx.mod.o
> xxx.mod.c:18:16: warning: initializer-string for array of chars is too long
> but it's merely a warning.
Thanks, applied!
Cheers,
Rusty.
>
> This patch adds the check of the symbol length in modpost and stops
> the build properly.
>
> Currently MODULE_NAME_LEN is defined in modpost.c instead of referring
> to the definition in kernel header because including linux/module.h is
> messy and we must cover cross-compilation.
>
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> ---
> v1->v2: Fix MODULE_NAME_LEN to use Elf_Addr
>
> scripts/mod/modpost.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c
> index 12d3db3bd46b..d583c98fde31 100644
> --- a/scripts/mod/modpost.c
> +++ b/scripts/mod/modpost.c
> @@ -2133,6 +2133,11 @@ static void add_staging_flag(struct buffer *b, const char *name)
> buf_printf(b, "\nMODULE_INFO(staging, \"Y\");\n");
> }
>
> +/* In kernel, this size is defined in linux/module.h;
> + * here we use Elf_Addr instead of long for covering cross-compile
> + */
> +#define MODULE_NAME_LEN (64 - sizeof(Elf_Addr))
> +
> /**
> * Record CRCs for unresolved symbols
> **/
> @@ -2177,6 +2182,12 @@ static int add_versions(struct buffer *b, struct module *mod)
> s->name, mod->name);
> continue;
> }
> + if (strlen(s->name) >= MODULE_NAME_LEN) {
> + merror("too long symbol \"%s\" [%s.ko]\n",
> + s->name, mod->name);
> + err = 1;
> + break;
> + }
> buf_printf(b, "\t{ %#8x, __VMLINUX_SYMBOL_STR(%s) },\n",
> s->crc, s->name);
> }
> --
> 2.5.0
prev parent reply other threads:[~2015-08-09 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 6:55 [PATCH v2] modpost: abort if a module symbol is too long Takashi Iwai
2015-08-08 5:47 ` Rusty Russell [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=87io8qbabs.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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.