Re: tun issue after e0b46d0ee9c: tun: Use iovec iterators
From: Marcelo Ricardo Leitner <hidden>
Date: 2014-12-01 13:06:01
On 30-11-2014 06:21, Herbert Xu wrote:
On Sat, Nov 29, 2014 at 03:08:09AM -0200, Marcelo Ricardo Leitner wrote:quoted
On 28-11-2014 21:59, Herbert Xu wrote:quoted
On Fri, Nov 28, 2014 at 05:25:27PM -0200, Marcelo Ricardo Leitner wrote:quoted
I saw there are tun updates on Dave's queue but none seemed to handle this. I can't use current net-next (799d2fff1858004526ad75d66a5dd8a5cce6ad40) on a kvm hypervisor because tun got clogged somehow. Bisected down to: commit e0b46d0ee9c240c7430a47e9b0365674d4a04522 Author: Herbert Xu [off-list ref] Date: Fri Nov 7 21:22:23 2014 +0800Does this patch help?Yay, it does! Works for me, thanks Herbert. I didn't test performance, but dhcp could get through. Are you sure about the Fixes tag? Because bisect really pointed to e0b46d0ee9c.Well according to your report you were having problems with tun_get_user. The bug I introduced was in tun_put_user and has already been fixed by Jason Wang.
Ahh yes, ok. Thanks Cheers, Marcelo