From: Zoltan Kiss <zoltan.kiss@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>, Wei Liu <wei.liu2@citrix.com>
Cc: <netdev@vger.kernel.org>, <xen-devel@lists.xen.org>,
<paul.durrant@citrix.com>, <edwin@etorok.net>,
Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [Xen-devel] [PATCH net] xen-netback: disable rogue vif in kthread context
Date: Mon, 24 Mar 2014 13:17:47 +0000 [thread overview]
Message-ID: <5330307B.8050304@citrix.com> (raw)
In-Reply-To: <533029C7.1080006@citrix.com>
On 24/03/14 12:49, David Vrabel wrote:
> On 24/03/14 12:13, Wei Liu wrote:
>> --- a/drivers/net/xen-netback/interface.c
>> +++ b/drivers/net/xen-netback/interface.c
>> @@ -62,6 +62,13 @@ static int xenvif_poll(struct napi_struct *napi, int budget)
>> struct xenvif *vif = container_of(napi, struct xenvif, napi);
>> int work_done;
>>
>> + /* This vif is rogue, we pretend we've used up all budget to
>> + * deschedule it from NAPI. But this interface will be turned
>> + * off in thread context later.
>> + */
>> + if (unlikely(vif->disabled))
>> + return budget;
>
> Shouldn't you call __napi_complete() and return 0? Returning budget
> will make NAPI poll repeatedly (since you're pretending to do work).
The comment in net_rx_action:
/* Drivers must not modify the NAPI state if they
* consume the entire weight. In such cases this code
* still "owns" the NAPI instance and therefore can
* move the instance around on the list at-will.
*/
>
>> diff --git a/drivers/net/xen-netback/netback.c b/drivers/net/xen-netback/netback.c
>> index 438d0c0..94e7261 100644
>> --- a/drivers/net/xen-netback/netback.c
>> +++ b/drivers/net/xen-netback/netback.c
>> @@ -655,7 +655,7 @@ static void xenvif_tx_err(struct xenvif *vif,
>> static void xenvif_fatal_tx_err(struct xenvif *vif)
>> {
>> netdev_err(vif->dev, "fatal error; disabling device\n");
>> - xenvif_carrier_off(vif);
>> + vif->disabled = true;
>
> Do you need to wake the thread here?
>
>> @@ -1549,6 +1549,16 @@ int xenvif_kthread(void *data)
>> wait_event_interruptible(vif->wq,
>> rx_work_todo(vif) ||
>> kthread_should_stop());
>
> || vif->disabled ?
>
>> +
>> + /* This frontend is found to be rogue, disable it in
>> + * kthread context. Currently this is only set when
>> + * netback finds out frontend sends malformed packet,
>> + * but we cannot disable the interface in softirq
>> + * context so we defer it here.
>> + */
>> + if (unlikely(vif->disabled) && netif_carrier_ok(vif->dev))
>> + xenvif_carrier_off(vif);
>> +
>> if (kthread_should_stop())
>> break;
>>
>
> As an aside, since I happened to be looking at xenvif_poll(), disabling
> local irqs to avoid problems with concurrent events looks unsafe as the
> event may occur on another VCPU.
>
> __napi_complete(napi);
> RING_FINAL_CHECK_FOR_REQUESTS(&vif->tx, more_to_do);
> if (more_to_do)
> napi_schedule(napi);
>
> Would work I think.
>
> David
>
next prev parent reply other threads:[~2014-03-24 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 12:13 [PATCH net] xen-netback: disable rogue vif in kthread context Wei Liu
2014-03-24 12:22 ` Ian Campbell
2014-03-24 12:33 ` David Laight
2014-03-24 12:49 ` [Xen-devel] " David Vrabel
2014-03-24 13:17 ` Zoltan Kiss [this message]
2014-03-25 0:55 ` Wei Liu
2014-03-24 19:29 ` David Miller
2014-03-25 0:44 ` [Xen-devel] " Wei Liu
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=5330307B.8050304@citrix.com \
--to=zoltan.kiss@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=edwin@etorok.net \
--cc=ian.campbell@citrix.com \
--cc=netdev@vger.kernel.org \
--cc=paul.durrant@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).