From: "David S. Miller" <davem@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: ak@muc.de, simon.roscic@chello.at, linux-kernel@vger.kernel.org,
netdev@oss.sgi.com
Subject: Re: [2.6.0-test8/9] ethertap oops
Date: Mon, 27 Oct 2003 04:22:58 -0800 [thread overview]
Message-ID: <20031027042258.21446129.davem@redhat.com> (raw)
In-Reply-To: <20031027122635.GB16013@wotan.suse.de>
On Mon, 27 Oct 2003 13:26:35 +0100
Andi Kleen <ak@suse.de> wrote:
> I don't know if it actually fixed the bug, I did not test it
> (sorry, should have stated that in the original mail)
> But at least it should printk now instead of crashing.
Ok, it's still an improvement over the blind dereferencing
it does not.
next prev parent reply other threads:[~2003-10-27 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <L1fo.3gb.9@gated-at.bofh.it>
2003-10-26 22:45 ` [2.6.0-test8/9] ethertap oops Andi Kleen
2003-10-27 7:48 ` David S. Miller
[not found] ` <20031027122635.GB16013@wotan.suse.de>
2003-10-27 12:22 ` David S. Miller [this message]
2003-10-27 17:40 ` Simon Roscic
2003-10-27 12:26 ` Andi Kleen
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=20031027042258.21446129.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@muc.de \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=simon.roscic@chello.at \
/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;
as well as URLs for NNTP newsgroup(s).