On Friday 20 Aug 2010 04:38:17 Eric Paris wrote: > On Fri, 2010-08-20 at 01:41 +0200, Andreas Gruenbacher wrote: > > (2) Construct a file descriptor that refers to the file that could not > > be > > > > dentry_open()ed, but which cannot be used for any I/O, and pass the > > error condition in a separate field. The kernel has all the > > information needed for doing that, and it shouldn't be hard to > > implement. > > > > That way, the listener always has a file descriptor to poke around > > with. > > > > Failing to do (2) right now, I think it still makes sense to separate the > > file descriptor from the error code in struct fanotify_event_metadata; > > this would enable us to do (2) later if we decide to. > > In reference to (2), I don't even understand what an fd is that can't be > used for anything. I'll let Al or Christoph respond if they feel like > it, but it sounds crazy to me. You want to just magic up some struct > file and attach a struct path to it even though dentry_open() failed? > So you can do what with it? I think Andreas would like to get a path even if open failed so it could be for that use? If creating such file object will be impossible or too hacky, but the general idea accepted, it may be better just to attach the path to the event. Tvrtko Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom. Company Reg No 2096520. VAT Reg No GB 348 3873 20. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
