From: Sasha Levin <levinsasha928@gmail.com>
To: rusty@rustcorp.com.au
Cc: linux-kernel@vger.kernel.org,
Sasha Levin <sasha.levin@oracle.com>,
Tim Abbott <tim.abbott@oracle.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] module: Remove module size limit
Date: Mon, 30 Jan 2012 23:13:08 -0500 [thread overview]
Message-ID: <1327983188.6697.9.camel@lappy> (raw)
In-Reply-To: <1327982842-13898-1-git-send-email-sasha.levin@oracle.com>
Rusty,
I'm not sure why git forgot to add the 'From' line, but if you do merge
it please add:
From: Sasha Levin <sasha.levin@oracle.com>
Thanks!
On Mon, 2012-01-30 at 23:07 -0500, Sasha Levin wrote:
> Module size was limited to 64MB, this was legacy limitation due to vmalloc()
> which was removed a while ago.
>
> Limiting module size to 64MB is both pointless and affects real world use
> cases.
>
> Cc: Rusty Russell <rusty@rustcorp.com.au>
> Cc: Tim Abbott <tim.abbott@oracle.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
> ---
> kernel/module.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/module.c b/kernel/module.c
> index 2c93276..3d56b6f 100644
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -2380,8 +2380,7 @@ static int copy_and_check(struct load_info *info,
> return -ENOEXEC;
>
> /* Suck in entire file: we'll want most of it. */
> - /* vmalloc barfs on "unusual" numbers. Check here */
> - if (len > 64 * 1024 * 1024 || (hdr = vmalloc(len)) == NULL)
> + if ((hdr = vmalloc(len)) == NULL)
> return -ENOMEM;
>
> if (copy_from_user(hdr, umod, len) != 0) {
--
Sasha.
next prev parent reply other threads:[~2012-01-31 4:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 4:07 [PATCH] module: Remove module size limit Sasha Levin
2012-01-31 4:13 ` Sasha Levin [this message]
2012-01-31 14:07 ` Josh Boyer
2012-01-31 15:27 ` Sasha Levin
2012-02-03 3:41 ` Rusty Russell
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=1327983188.6697.9.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.org \
--cc=tim.abbott@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox