From: "Alexander V. Lukyanov" <lav@netis.ru>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: 2.6.0-test9: access beyond end of device
Date: Thu, 30 Oct 2003 14:02:59 +0300 [thread overview]
Message-ID: <20031030110258.GA13681@night.netis.priv> (raw)
In-Reply-To: <20031030013904.6acaefe3.akpm@osdl.org>
On Thu, Oct 30, 2003 at 01:39:04AM -0800, Andrew Morton wrote:
> Congratulations, you broke the 2.6 networking code!
Probably not. I have found a problem in ip_wccp module which I have loaded.
It used ip_rcv while netif_rx is the proper function to use.
After I have fixed that, linux-2.6.0-test9 works well. Sorry for confusion.
I'll report if I find other problems. Thanks!
--
Alexander.
prev parent reply other threads:[~2003-10-30 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031029101240.GA12958@night.netis.priv>
[not found] ` <20031029124003.4510bb1d.akpm@osdl.org>
[not found] ` <20031030092248.GA7649@swing.yars.free.net>
2003-10-30 9:39 ` 2.6.0-test9: access beyond end of device Andrew Morton
2003-10-30 11:02 ` Alexander V. Lukyanov [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=20031030110258.GA13681@night.netis.priv \
--to=lav@netis.ru \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).