From: "David S. Miller" <davem@redhat.com>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH?] Fix sniffing of ARP replies
Date: Fri, 17 Oct 2003 00:10:13 -0700 [thread overview]
Message-ID: <20031017001013.306f1cd2.davem@redhat.com> (raw)
In-Reply-To: <20031015171112.GA2469@vana.vc.cvut.cz>
On Wed, 15 Oct 2003 19:11:12 +0200
Petr Vandrovec <vandrove@vc.cvut.cz> wrote:
> - (struct sock *)ptype->af_packet_priv != skb->sk) {
> + (ptype->af_packet_priv == NULL ||
> + (struct sock *)ptype->af_packet_priv != skb->sk)) {
Ok, after studying this some more, I think this patch makes
sense and I'll apply it to 2.6.x
Thanks for being patient with my idiocy this afternoon.
:-)
next prev parent reply other threads:[~2003-10-17 7:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 17:11 [PATCH?] Fix sniffing of ARP replies Petr Vandrovec
2003-10-16 3:47 ` David S. Miller
2003-10-17 7:10 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-16 10:07 Petr Vandrovec
2003-10-16 22:21 ` David S. Miller
2003-10-16 22:41 ` Joe Perches
2003-10-16 22:45 ` David S. Miller
2003-10-16 23:48 ` Petr Vandrovec
2003-10-17 6:55 ` David S. Miller
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=20031017001013.306f1cd2.davem@redhat.com \
--to=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=vandrove@vc.cvut.cz \
/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).