[lkml]   [2002]   [Sep]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC] Raceless module interface

On Fri, 13 Sep 2002, Daniel Phillips wrote:

> > The exit function should always be called after the init function (even if
> > it failed, I don't do it in the patch, that's a bug). The fs init/exit
> > would like this then:
> Perhaps, but if so, the module itself should call the exit function in
> its failure path itself. Doing the full exit whether it needs to be
> done or not is wasteful and opens up new DoS opportunities.

The exit itself can fail as well, so it has to be done by the module code
anyway (until it suceeds).
What DoS opportunities are there? Module init failure is the exception
case and usally needs further attention, so we could actually disable
further attempts to load this module, unless the user tells us
specifically so.

> In the example you give below you must rely on register_filesystem
> tolerating unregistering a nonexistent filesystem. That's sloppy at
> best, and you will have to ensure *every* helper used by ->exit is
> similarly sloppy.

Why is that sloppy? E.g. kfree() happily accepts NULL pointers as well.

bye, Roman

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.185 / U:0.872 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site