From: David Miller <davem@davemloft.net>
To: a1k@mail.ru
Cc: netdev@vger.kernel.org, miquels@drinkel.ow.org
Subject: Re: AF_PACKET + PACKET_FANOUT: tx packet delivered back in rx
Date: Thu, 16 Aug 2012 14:53:22 -0700 (PDT) [thread overview]
Message-ID: <20120816.145322.1154793898136345258.davem@davemloft.net> (raw)
In-Reply-To: <1342081817.394175102@f168.mail.ru>
From: Aleksandr Kotov <a1k@mail.ru>
Date: Thu, 12 Jul 2012 12:30:17 +0400
> I have a problem using AF_PACKET socket with PACKET_RX_RING, PACKET_TX_RING and PACKET_FANOUT options enabled.
> I am seeing my TX packets get back to the same socket in RX ring. Socket is created and gets bind with ETH_P_ALL protocol type. The problem is in the fanout_add function
> which sets af_packet_priv to "match" variable, but not sk one describing socket and in dev_queue_xmit_nit skb get bounced back to the socket despite the comment left in the function.
Eric Leblong is posting fixes for this problem recently:
http://patchwork.ozlabs.org/patch/178044/
prev parent reply other threads:[~2012-08-16 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 8:30 AF_PACKET + PACKET_FANOUT: tx packet delivered back in rx Aleksandr Kotov
2012-08-16 21:53 ` David Miller [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=20120816.145322.1154793898136345258.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a1k@mail.ru \
--cc=miquels@drinkel.ow.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).