xen-netback: don't de-reference vif pointer after having called xenvif_put()
When putting vif-s on the rx notify list, calling xenvif_put() must be deferred until after the removal from the list and the issuing of the notification, as both operations dereference the pointer. Changing this got me to notice that the "irq" variable was effectively unused (and was of too narrow type anyway). Signed-off-by: Jan Beulich <jbeulich@suse.com> Acked-by: Ian Campbell <ian.campbell@citrix.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
99ffc3e74f
commit
94f950c406
1 changed files with 6 additions and 5 deletions
|
@ -662,7 +662,7 @@ static void xen_netbk_rx_action(struct xen_netbk *netbk)
|
|||
{
|
||||
struct xenvif *vif = NULL, *tmp;
|
||||
s8 status;
|
||||
u16 irq, flags;
|
||||
u16 flags;
|
||||
struct xen_netif_rx_response *resp;
|
||||
struct sk_buff_head rxq;
|
||||
struct sk_buff *skb;
|
||||
|
@ -771,13 +771,13 @@ static void xen_netbk_rx_action(struct xen_netbk *netbk)
|
|||
sco->meta_slots_used);
|
||||
|
||||
RING_PUSH_RESPONSES_AND_CHECK_NOTIFY(&vif->rx, ret);
|
||||
irq = vif->irq;
|
||||
if (ret && list_empty(&vif->notify_list))
|
||||
list_add_tail(&vif->notify_list, ¬ify);
|
||||
|
||||
xenvif_notify_tx_completion(vif);
|
||||
|
||||
xenvif_put(vif);
|
||||
if (ret && list_empty(&vif->notify_list))
|
||||
list_add_tail(&vif->notify_list, ¬ify);
|
||||
else
|
||||
xenvif_put(vif);
|
||||
npo.meta_cons += sco->meta_slots_used;
|
||||
dev_kfree_skb(skb);
|
||||
}
|
||||
|
@ -785,6 +785,7 @@ static void xen_netbk_rx_action(struct xen_netbk *netbk)
|
|||
list_for_each_entry_safe(vif, tmp, ¬ify, notify_list) {
|
||||
notify_remote_via_irq(vif->irq);
|
||||
list_del_init(&vif->notify_list);
|
||||
xenvif_put(vif);
|
||||
}
|
||||
|
||||
/* More work to do? */
|
||||
|
|
Loading…
Reference in a new issue