Re: [RFC][PATCH] fs: configfs: programmatically create config groups

[Sebastian Andrzej Siewior]

On 11/28/2012 02:05 PM, Michal Nazarewicz wrote:
> > On 11/27/2012 05:23 PM, Michal Nazarewicz wrote:
> > > How should a generic tool know what kind of actions are needed for given
> > > function to be removed?  If you ask me, there should be a way to unbind
> > > gadget and unload all modules without any specific knowledge of the
> > > functions.  If there is no such mechanism, then it's a bad user
> > > interface.
>
> On Wed, Nov 28 2012, Sebastian Andrzej Siewior wrote:
> > Well. You need only to remove the directories you created.
>
> My point is that there should be a way to write a script that is unaware
> of the way function is configured, ie. which directories were created
> and which were not.

I get this. If you recursively rmdir each directory then you clean it
up.

> Besides, if you rmdir lun0, is the function still supposed to work with
> all LUNs present?  In my opinion, while gadget is bound, it should not
> be possible to modify such things.

That is correct. The configuration should remain frozen as long as the
gadget is active because in most cases you can't propagate the change.

> > An unbind would be  simply an unlink of the gadget  which is linked to
> > the udc.   All configurations  remain so  you can link  it at  a later
> > point without touching the configuration because it is as it was.
>
> Yes, but that's not my concern.  My concern is that I should be able to
> put a relatively simple code in my shutdown script (or whatever) which
> unbinds all gadgets, without knowing what kind of functions are used.
>
> And I'm proposing that this could be done by allowing user to just do:
>
> 	cd /cfs/...
> 	rmdir gadgets/*		# unbind and remove all gadgets
> 	rmdir functions/*/*	# unbind and remove all function instances
> 	rmdir functions/*	# unload all functions

Yes, you push for simple rmdir API. That would avoid the need for an
user land tool at some point and you end up in shell scripts.
I'm not against it but others do have user tools to handle such things.
Anyway, for this to work we have to go through Joel.

> 	rmdir udcs/*		# unload all UDCs

No, for this you still have to rmmod :)


> > > I think the question is of information flow direction.  If user gives
> > > some information to the kernel, she should be the one creating any
> > > necessary directories.  But if the information comes from kernel to the
> > > user, the kernel should create the structure.
>
> > Yes that is a point. But the "name" can go away if we use it in the
> > directory name. That is what other configfs user do. The same is true
> > for luns for instance. I just want to avoid adding features because we
> > do something different compared to every other configfs user.
>
> You've lost me here.  What are we talking about again?  What ânameâ are
> you referring to?

           <function_name>-<common_name>
/functions/acm-function/

instead of
           <common_name>
/functions/function1/
                     +name
with attribute file named "name" which contains the name of the
function (i.e. acm). My point is to keep "name" in the directory name
instead having an extra attribute.

Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/