lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 29 Nov 2008 10:18:49 +0000 From: James Le Cuirot <chewi@...a-online.co.uk> To: Max Krasnyansky <maxk@...lcomm.com> Cc: "Rafael J. Wysocki" <rjw@...k.pl>, suspend-devel@...ts.sourceforge.net, LKML <linux-kernel@...r.kernel.org>, pm list <linux-pm@...ts.linux-foundation.org>, netdev@...r.kernel.org Subject: Re: [Suspend-devel] TAP (and TUN?) devices not working after resume On Thu, 24 Jul 2008 20:50:32 -0700 Max Krasnyansky <maxk@...lcomm.com> wrote: > > On Monday, 14 of July 2008, James Le Cuirot wrote: > >> > >> Hi, > >> > >> uswsusp works great on my machine except for one thing. I use a TAP > >> device for QEMU and after resuming from suspend, it doesn't work > >> anymore until I delete it and recreate it. This is rather annoying > >> because if I have QEMU open, it means I have to close it before > >> recreating the interface and then boot Windows up again. I use > >> OpenVPN to create/delete the interface but I think that's all it > >> does. The rest is done by the kernel. So I'm guessing something's > >> up with the TUN/TAP driver or uswsusp itself. I'm using version > >> 0.8. Sorry if this has already been fixed. > > I bet it's flow control related. I've fixed a bug in flow control > handling for persistent devices recently. > btw Does it still happen with >= 2.6.26 ? > > I'll play with some test code on my laptop and see if I can reproduce > this issue. > > Max Sorry about the crazy delay here, I didn't need to use QEMU for ages and I don't like firing up Windows unless I have too. :D I'm not sure about 2.6.26 but this appears to be fixed in 2.6.27. Thanks, James -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists