Prev: Rebase v. merge (Was: Re: linux-next: manual merge of the xfs tree with the vfs tree)
Next: dmac_*_range vs. outer_*_range ?
From: Ed Swierk on 15 Feb 2010 18:50
On Sat, Feb 13, 2010 at 2:33 AM, Arnd Bergmann <arnd(a)arndb.de> wrote:
> The original macvtap code has a number of problems
> resulting from the use of RCU for protecting the
> access to struct macvtap_queue from open files.
>
> This includes
> - need for GFP_ATOMIC allocations for skbs
> - potential deadlocks when copy_*_user sleeps
> - inability to work with vhost-net
>
> Changing the lifetime of macvtap_queue to always
> depend on the open file solves all these. The
> RCU reference simply moves one step down to
> the reference on the macvlan_dev, which we
> only need for nonblocking operations.
>
> Signed-off-by: Arnd Bergmann <arnd(a)arndb.de>

This works for me.

Acked-by: Ed Swierk <eswierk(a)aristanetworks.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: Rebase v. merge (Was: Re: linux-next: manual merge of the xfs tree with the vfs tree)
Next: dmac_*_range vs. outer_*_range ?