From: Oleg Drokin <green@dredd.crimea.edu>
To: linux-kernel@vger.kernel.org, davem@redhat.com, kuznet@ms2.inr.ac.ru
Subject: IP layer bug?
Date: Sun, 25 Mar 2001 00:57:31 +0300 [thread overview]
Message-ID: <20010325005731.A5243@dredd.crimea.edu> (raw)
Hello!
2.4.x kernel. have not tried 2.2
I just found somethig, I believe is kernel bug.
I am working with usbnet.c driver, which stores some of its
internal state in sk_buff.cb area. But once such skb passed to
upper layer with netif_rx, net/ipv4/ip_input.c reuses content of cb
(line #345), and all packets that should go outside of beyond hosts
we have direct routes to, fails, because we think, they have source routing
enabled.
For now I workarounded it with filling skb->cb with zeroes before
netif_rx(), but I believe it is a kludge and networking layer should be fixed
instead.
Thank you.
Bye,
Oleg
next reply other threads:[~2001-03-24 21:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-24 21:57 Oleg Drokin [this message]
2001-03-26 10:36 ` IP layer bug? Manoj Sontakke
2001-03-26 6:09 ` Oleg Drokin
2001-03-26 12:21 ` Manoj Sontakke
2001-03-26 7:02 ` Oleg Drokin
2001-03-30 17:13 ` kuznet
2001-03-31 15:03 ` Oleg Drokin
2001-03-31 15:32 ` kuznet
2001-04-02 9:25 ` Oleg Drokin
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=20010325005731.A5243@dredd.crimea.edu \
--to=green@dredd.crimea.edu \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--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