From: "Serge Kuznetsov" <sk@deeptown.org>
To: "David S. Miller" <davem@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-net@vger.kernel.org>
Subject: Re: [NET] Possible bug in netif_receive_skb
Date: Thu, 14 Nov 2002 15:15:26 -0500 [thread overview]
Message-ID: <002d01c28c1a$91ff9640$34c096cd@toybox> (raw)
In-Reply-To: 20021114.092646.38763468.davem@redhat.com
>
> ->func() must either take or free up the SKB, there must be no
> violations of this rule.
>
Could you explain it more clearly?
How it applies to that two ( even three ) scenarios, I've told?
What if we have the first scenario:
ptype_all->func = func1;
ptype_all->next = NULL;
Will this function be called or not?
Second scenario:
ptype_all->func = func1;
ptype_all->next = &ptype1;
ptype1->func = func2;
ptype1->next = NULL;
Will func2() be called?
Third scenario:
ptype_all->func = func1;
ptype_all->next = &ptype1;
ptype1->func = func2;
ptype1->next = &ptype2;
ptype2->func = func3;
ptype2->next = &ptype3;
ptype3->func = func4;
ptype3->next = NULL;
If func2() freed skb, and return NET_RX_DROP, what will happen?
PS: I still don't understand why we should skip the first step, and call first function on second cycle?
next prev parent reply other threads:[~2002-11-14 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 17:12 [NET] Possible bug in netif_receive_skb Serge Kuznetsov
2002-11-14 17:26 ` David S. Miller
2002-11-14 20:15 ` Serge Kuznetsov [this message]
2002-11-14 18:00 ` Arnaldo Carvalho de Melo
2002-11-15 14:10 ` Serge Kuznetsov
-- strict thread matches above, loose matches on Subject: below --
2002-11-14 21:05 Serge Kuznetsov
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='002d01c28c1a$91ff9640$34c096cd@toybox' \
--to=sk@deeptown.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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