linux-kernel - Re: [RFC 0/2] USB gadget

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <502CF9E3.2010608@linutronix.de>
Date:	Thu, 16 Aug 2012 15:47:15 +0200
From:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:	Andrzej Pietrasiewicz <andrzej.p@...sung.com>
CC:	'Joel Becker' <jlbec@...lplan.org>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	'Kyungmin Park' <kyungmin.park@...sung.com>,
	'Felipe Balbi' <balbi@...com>,
	'Greg Kroah-Hartman' <gregkh@...uxfoundation.org>,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	'Alan Stern' <stern@...land.harvard.edu>
Subject: Re: [RFC 0/2] USB gadget - configfs

On 08/16/2012 03:17 PM, Andrzej Pietrasiewicz wrote:
> A lun is "opened" on storing the "file" attribute of the lun, it is in
> fsg_lun_store_file, storage_common.c. So, again, this is a configfs
> callback.
>
> On storing the connect attribute, the following happens: a composite driver
> is probed, then all the configurations are iterated over, their functions
> being bound in turn. After the gadget is set up this way, the host notices
> connecting a new mass storage device.

The configuration has to remain unchanged until the "connect" attribute
is changed (i.e. unconnected). That means the gadget can only be
reconfigured once it is not active.

> So it seems the only chance to call config_item_depend is in a configfs
> callback. Or is it?
>
> Thanks,
>
> Andrzej

Sebastian
--
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/