On Tue, Dec 05, 2006 at 10:02:10PM +0100, Jan Engelhardt wrote:
> On Dec 4 2006 07:30, Josef 'Jeff' Sipek wrote:
> >+long unionfs_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
> >+{
> >+ long err;
> >+
> >+ if ((err = unionfs_file_revalidate(file, 1)))
> >+ goto out;
> >+
> >+ /* check if asked for local commands */
> >+ switch (cmd) {
> >+ case UNIONFS_IOCTL_INCGEN:
> >+ /* Increment the superblock generation count */
> >+ err = -EACCES;
> >+ if (!capable(CAP_SYS_ADMIN))
> >+ goto out;
> >+ err = unionfs_ioctl_incgen(file, cmd, arg);
> >+ break;
> >+
> >+ case UNIONFS_IOCTL_QUERYFILE:
> >+ /* Return list of branches containing the given file */
> >+ err = unionfs_ioctl_queryfile(file, cmd, arg);
> >+ break;
> >+
> >+ default:
> >+ /* pass the ioctl down */
> >+ err = do_ioctl(file, cmd, arg);
> >+ break;
> >+ }
> >+
> >+out:
> >+ return err;
> >+}
>
>
> I think there was an ioctl for files to find out where a particular
> file lives on disk.
That's the UNIONFS_IOCTL_QUERYFILE case.
> Do you think unionfs should handle it and return
> something more or less meaningful?
It is a very useful functionality for any stackable filesystem which may
store files on one of several branches. Do I think that it should be
factored out of Unionfs into fsstack or similar? Not at the moment. If there
seems to be a need for it, then I'd gladly move it out of Unionfs, but until
then I don't see a reason to do anything special.
Josef "Jeff" Sipek.
--
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are, by
definition, not smart enough to debug it.
- Brian W. Kernighan
-
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
