[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180521.114742.427929977852677864.davem@davemloft.net>
Date: Mon, 21 May 2018 11:47:42 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: jasowang@...hat.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
mst@...hat.com, hannes@...essinduktion.org, edumazet@...gle.com
Subject: Re: [PATCH net] tuntap: raise EPOLLOUT on device up
From: Jason Wang <jasowang@...hat.com>
Date: Fri, 18 May 2018 21:00:43 +0800
> We return -EIO on device down but can not raise EPOLLOUT after it was
> up. This may confuse user like vhost which expects tuntap to raise
> EPOLLOUT to re-enable its TX routine after tuntap is down. This could
> be easily reproduced by transmitting packets from VM while down and up
> the tap device. Fixing this by set SOCKWQ_ASYNC_NOSPACE on -EIO.
>
> Cc: Hannes Frederic Sowa <hannes@...essinduktion.org>
> Cc: Eric Dumazet <edumazet@...gle.com>
> Fixes: 1bd4978a88ac2 ("tun: honor IFF_UP in tun_get_user()")
> Signed-off-by: Jason Wang <jasowang@...hat.com>
I'm no so sure what to do with this patch.
Like Michael says, this flag bit is only checks upon transmit which
may or may not happen after this point. It doesn't seem to be
guaranteed.
Powered by blists - more mailing lists