From: Andi Kleen <ak@muc.de>
To: Rick Jones <rick.jones2@hp.com>
Cc: Neil Horman <nhorman@redhat.com>, jamal <hadi@cyberus.ca>,
linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: Must every packet have a creating socket?
Date: Fri, 22 Apr 2005 13:39:46 +0200 [thread overview]
Message-ID: <m1d5snyr99.fsf@muc.de> (raw)
In-Reply-To: <4266FFC4.6020305@hp.com> (Rick Jones's message of "Wed, 20 Apr 2005 18:20:04 -0700")
Rick Jones <rick.jones2@hp.com> writes:
>> Can I think that every packet (e.g. IP packet) must
>> have a corresponding creating socket? (i.e. Must every
>> packet be created by a socket?)
>
> No. ICMP messages come to mind - although I _suppose_ that since
> those are in response to other traffic, you could claim it was in
> response to something sent from a "socket" or "endpoint" - depends on
> how far away you consider it to still be from a socket.
Actually Linux has kernel private sockets for ICMP.
Very old Linux didnt, but it required ugly special cases
in the transmit path, so it was removed.
-Andi
prev parent reply other threads:[~2005-04-22 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 17:29 Must every packet have a creating socket? (was Re: Does a forwarded packet has a local socket with it?) Park Lee
2005-04-21 1:20 ` Rick Jones
2005-04-22 11:39 ` Andi Kleen [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=m1d5snyr99.fsf@muc.de \
--to=ak@muc.de \
--cc=hadi@cyberus.ca \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=nhorman@redhat.com \
--cc=rick.jones2@hp.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).