From: Alexander Duyck <alexander.duyck@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>,
Alexander Duyck <alexander.h.duyck@intel.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH] net: Validate frames going through the direct_xmit path
Date: Tue, 02 Sep 2014 19:46:34 -0700 [thread overview]
Message-ID: <5406810A.9070900@gmail.com> (raw)
In-Reply-To: <1409700648.26422.21.camel@edumazet-glaptop2.roam.corp.google.com>
On 09/02/2014 04:30 PM, Eric Dumazet wrote:
> On Tue, 2014-09-02 at 18:55 -0400, Alexander Duyck wrote:
>> In commit 50cbe9ab5f8d92d2d4a327b56e96559d8f63a1fa "net: Validate xmit SKBs
>> right when we pull them out of the qdisc" the validation code was moved out
>> of dev_hard_start_xmit and into dequeue_skb. However this overlooked the
>> fact that we do not always enqueue the skb onto a qdisc.
>>
>> As a result I was seeing issues trying to connect to a vhost_net interface
>> after this patch was applied. To resolve the issue I have added a call to
>> validate_xmit_skb in sched_direct_xmit and this seems to have resolved the
>> issue by restoring the validation to this xmit path.
>>
>> Signed-off-by: Alexander Duyck <alexander.h.duyck@intel.com>
>> ---
>> net/sched/sch_generic.c | 9 +++++++--
>> 1 file changed, 7 insertions(+), 2 deletions(-)
>>
>> diff --git a/net/sched/sch_generic.c b/net/sched/sch_generic.c
>> index a8bf9f9..203ee65 100644
>> --- a/net/sched/sch_generic.c
>> +++ b/net/sched/sch_generic.c
>> @@ -128,8 +128,13 @@ int sch_direct_xmit(struct sk_buff *skb, struct Qdisc *q,
>> spin_unlock(root_lock);
>>
>> HARD_TX_LOCK(dev, txq, smp_processor_id());
>> - if (!netif_xmit_frozen_or_stopped(txq))
>> - skb = dev_hard_start_xmit(skb, dev, txq, &ret);
>> + if (!netif_xmit_frozen_or_stopped(txq)) {
>> + skb = validate_xmit_skb(skb, dev);
>> + if (!skb)
>> + ret = NETDEV_TX_OK;
>> + else
>> + skb = dev_hard_start_xmit(skb, dev, txq, &ret);
>> + }
>>
>> HARD_TX_UNLOCK(dev, txq);
>>
>
> This looks very weird.
It's ugly, I will admit it. It was a quick hack to fix the issue I had
been seeing as it was in my way.
> Calling validate_xmit_skb() twice per packet is not needed in the case
> sch_direct_xmit() is called from qdisc_restart()
My bad, I overlooked that sch_direct_xmit is called by qdisc_restart.
> This will add bad branch prediction at very minimum.
>
> This is a TCQ_F_CAN_BYPASS issue that should be fixed there.
Actually it looks like there are several issues. One is the bypass
problem which is the major issue. Another side effect of the original
patch is that a bad frame will cause us to exit __qdisc_run prematurely
even if other frames are still in the qdisc.
Alternative patches always welcome. :-) My goal at this point is to
just have my vhost_net interface work so I can get back to my other
development work. I will submit a v2 in the morning if I don't see
anything.
Alex
next prev parent reply other threads:[~2014-09-03 2:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 22:55 [PATCH] net: Validate frames going through the direct_xmit path Alexander Duyck
2014-09-02 23:30 ` Eric Dumazet
2014-09-03 2:46 ` Alexander Duyck [this message]
2014-09-03 4:23 ` Eric Dumazet
2014-09-03 11:57 ` Jesper Dangaard Brouer
2014-09-03 11:48 ` [net-next PATCH] qdisc: validate " Jesper Dangaard Brouer
2014-09-03 13:43 ` Eric Dumazet
2014-09-03 13:52 ` Jesper Dangaard Brouer
2014-09-03 14:26 ` Jesper Dangaard Brouer
2014-09-03 15:22 ` Eric Dumazet
2014-09-03 15:24 ` [net-next PATCH V2] " Jesper Dangaard Brouer
2014-09-03 15:56 ` [net-next PATCH V3] " Jesper Dangaard Brouer
2014-09-03 16:08 ` Eric Dumazet
2014-09-03 16:17 ` Jesper Dangaard Brouer
2014-09-04 3:43 ` David 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=5406810A.9070900@gmail.com \
--to=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--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).