From: "Stephen C. Biggs" <s.biggs@softier.com>
To: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Bug in kernel code?
Date: Tue, 27 Aug 2002 18:24:13 -0700 [thread overview]
Message-ID: <3D6BC3CD.10889.6526BC@localhost> (raw)
In-Reply-To: <20020827.180953.122061677.davem@redhat.com>
On 27 Aug 2002 at 18:09, David S. Miller wrote:
> From: "Stephen C. Biggs" <s.biggs@softier.com>
> Date: Tue, 27 Aug 2002 18:09:46 -0700
>
> There need to be some sanity checks in this code: what if mempages is passed as some insanely huge
> number, e.g.
>
> And then your mail ends.... let us know when you've fixed
> your email client, this isn't rocket science :-)
>
What are you talking about "And then your mail ends..." That's all I wanted to say...
Oh, you want me to post a complete patch.... I get it.
next prev parent reply other threads:[~2002-08-28 1:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D6BB5C3.16057.2E515C@localhost>
[not found] ` <20020827.172304.22017977.davem@redhat.com>
2002-08-28 0:32 ` Bug in kernel code? Stephen C. Biggs
2002-08-28 0:29 ` David S. Miller
2002-08-28 0:40 ` Stephen C. Biggs
2002-08-28 0:42 ` David S. Miller
2002-08-28 1:09 ` Stephen C. Biggs
2002-08-28 1:09 ` David S. Miller
2002-08-28 1:24 ` Stephen C. Biggs [this message]
2002-08-28 1:23 ` David S. Miller
2002-08-28 2:42 ` Stephen C. Biggs
2002-08-28 3:39 ` David S. Miller
2002-08-28 3:57 ` Luca Barbieri
2002-08-28 3:58 ` David S. Miller
2002-08-28 4:10 ` Luca Barbieri
2002-08-28 4:07 ` David S. Miller
2002-08-28 4:29 ` Luca Barbieri
2002-08-28 4:29 ` Stephen Biggs
2002-08-28 4:26 ` David S. Miller
2002-08-28 21:54 ` H. Peter Anvin
2002-08-28 2:49 ` Re[2]: " Stephen C. Biggs
2002-08-28 0:54 ` Stephen C. Biggs
2002-08-28 0:25 Stephen C. Biggs
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=3D6BC3CD.10889.6526BC@localhost \
--to=s.biggs@softier.com \
--cc=davem@redhat.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