[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <000001cd85e8$b2c2f340$1848d9c0$%p@samsung.com>
Date: Wed, 29 Aug 2012 15:17:53 +0200
From: Andrzej Pietrasiewicz <andrzej.p@...sung.com>
To: 'Joel Becker' <jlbec@...lplan.org>,
'Sebastian Andrzej Siewior' <bigeasy@...utronix.de>
Cc: 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
Hello Joel,
On Monday, August 20, 2012 8:00 AM Joel Becker wrote:
<snip>
> I think what you want here is a symlink. Create a directory high in
> the tree called 'ready' or 'available', and when you want to lock the
> device in place, symlink it into that directory. This will pin the item.
> You can also make use of the ->allow_link() and ->drop_link() callbacks to
> prevent symlinking an item until it is fully configured, and prevent
> unlinking an item that is in use.
>
I have a question to you. In fs/configfs/dir.c, in a comment before
configfs_depend_item and configfs_depend_prep you say that "configfs uses
VFS to handle all locking". I am trying to understand how this
works. Could you please elaborate a bit about it? Which locks from VFS
handle "all locking"? When does locking happen?
Thanks,
Andrzej
--
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