| 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: <1921559.OPsFBnvatA@linux-lqwf.site> Date: Mon, 15 Oct 2012 14:30:57 +0200 From: Oliver Neukum <oneukum@...e.de> To: Ming Lei <ming.lei@...onical.com> Cc: linux-kernel@...r.kernel.org, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, linux-usb@...r.kernel.org, Alan Stern <stern@...land.harvard.edu> Subject: Re: [RFC PATCH 3/3] USB: forbid memory allocation with I/O during bus reset if storage interface exits On Monday 15 October 2012 20:06:36 Ming Lei wrote: > On Mon, Oct 15, 2012 at 5:34 PM, Oliver Neukum <oneukum@...e.de> wrote: > > > > I think limiting this to devices which have a storage device is not > > productive. What if you are using iSCSI or nbd? In the long run > > You mean other non-mass storage or non-uas usb interfaces may > be involved in iSCSI or nbd? If not, the patch should be OK. > If yes, could you list them? All network devices? > > we will see busses attached to busses and as soon as the daughter > > bus is hotpluggable you are thwarted anyway. Just do it unconditionally. > > IMO, doing it unconditionally is not good because big chunk buffer > is often allocated in probe() path. It would be a chunk that has just been freed. Regards Oliver -- 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