public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: joe.korty@ccur.com (Joe Korty)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] some large create_module(2) sizes can oops a kernel
Date: Mon, 13 Jan 2003 13:34:43 +1100	[thread overview]
Message-ID: <20030113031023.213EC2C06A@lists.samba.org> (raw)
In-Reply-To: Your message of "Sat, 11 Jan 2003 21:41:36 CDT." <200301120241.CAA16791@rudolph.ccur.com>

In message <200301120241.CAA16791@rudolph.ccur.com> you write:
> Hi Rusty aka trivial patch monkey, everyone,
> 
> The 2.4 kernel will oops when create_module(2) is passed a size of
> -1, -2, or any size larger than num_physpages.  The following patch
> is one of the many simple ways to fix this.  Please consider it or
> some variant for inclusion in 2.4.

How about removing the BUG() from vmalloc.c, like 2.5 has done?

Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2003-01-13  3:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-12  2:41 [PATCH] some large create_module(2) sizes can oops a kernel Joe Korty
2003-01-13  2:34 ` Rusty Russell [this message]
2003-01-13  3:59   ` Joe Korty

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=20030113031023.213EC2C06A@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=joe.korty@ccur.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