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: Fri, 11 Jan 2013 09:29:20 +0800 From: Jason Wang <jasowang@...hat.com> To: David Miller <davem@...emloft.net> CC: stefanha@...hat.com, mst@...hat.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 3.8-rc] tuntap: refuse to re-attach to different tun_struct On 01/11/2013 06:39 AM, David Miller wrote: > From: Stefan Hajnoczi <stefanha@...hat.com> > Date: Thu, 10 Jan 2013 08:59:48 +0100 > >> Multiqueue tun devices support detaching a tun_file from its tun_struct >> and re-attaching at a later point in time. This allows users to disable >> a specific queue temporarily. >> >> ioctl(TUNSETIFF) allows the user to specify the network interface to >> attach by name. This means the user can attempt to attach to interface >> "B" after detaching from interface "A". >> >> The driver is not designed to support this so check we are re-attaching >> to the right tun_struct. Failure to do so may lead to oops. >> >> Signed-off-by: Stefan Hajnoczi <stefanha@...hat.com> > Applied. Hi David: Any chance that I can have a respin on this patch, there's still a bug after this patch. Or I just can send a patch on top? Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists