Hi Everyone, I'm answering this from my home email. I have not heard from my co-workers in Florida yet, and I imagine that they are busy cleaning up after hurricane Katrina and waiting for the power to come back on.
It looks like we have an "off by one" problem with idr_get_new_above() which may be part of the inotify problem. I'm not sure if the problem is the behavior or the name & comments. The start_id parameter is the starting point for the idr allocation search, and if it is available, it will be allocated. If you pass in the last id allocated as the start_id and it has already been freed (by an idr_remove call), it will be allocated again. The obvious fix would be to increment start_id in idr_get_new_above(). I would be glad to spend some time looking at the inotify problem assuming that fixing the off-by-one problem above doesn't solve it. I have not used inotify and would need pointers to the user space header files and library. Jim - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
