From: jak@rudolph.ccur.com (Joe Korty)
To: rusty@rustcorp.com.au (Rusty Russell)
Cc: joe.korty@ccur.com (Joe Korty), linux-kernel@vger.kernel.org
Subject: Re: [PATCH] some large create_module(2) sizes can oops a kernel
Date: Sun, 12 Jan 2003 22:59:41 -0500 (EST) [thread overview]
Message-ID: <200301130359.DAA18113@rudolph.ccur.com> (raw)
In-Reply-To: <20030113031023.213EC2C06A@lists.samba.org> from "Rusty Russell" at Jan 13, 2003 01:34:43 PM
> How about removing the BUG() from vmalloc.c, like 2.5 has done?
I was erring on the safe side of assuming the BUG was useful for
detecting internal (non-user) erronous uses of vmalloc. However
if that is not an issue then removing the BUG is best.
Joe
prev parent reply other threads:[~2003-01-13 3:50 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
2003-01-13 3:59 ` Joe Korty [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=200301130359.DAA18113@rudolph.ccur.com \
--to=jak@rudolph.ccur.com \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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