| 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
| ||
|
Message-ID: <20130805175302.GJ5051@mwanda> Date: Mon, 5 Aug 2013 20:53:02 +0300 From: Dan Carpenter <dan.carpenter@...cle.com> To: Rupesh Gujare <rupesh.gujare@...el.com> Cc: devel@...uxdriverproject.org, gregkh@...uxfoundation.org, linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/4] staging: ozwpan: Increment port number for new device. On Mon, Aug 05, 2013 at 06:40:13PM +0100, Rupesh Gujare wrote: > This patch fixes crash issue when there is quick cycle of > de-enumeration & enumeration due to loss of wireless link. > > It is found that sometimes new device (or coming back device) > returns very fast, even before USB core read out hub status, > resulting in allocation of same port, which results in unstable > system & crash. > > Above issue is resolved by making sure that we always assign > new port to new device, making sure that USB core reads correct > hub status. > This feels like papering over the problem. Surely the real fix would be to improve the reference counting. This patch is probably effective but it makes the code more subtle and it shows that we don't really understand what we are doing with regards to reference counting. regards, dan carpenter -- 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