Re: [PATCH] vfs: new O_NODE open flag

From: Andreas Dilger
Date: Fri Sep 25 2009 - 15:02:35 EST


On Sep 25, 2009 13:20 -0400, Valdis.Kletnieks@xxxxxx wrote:
> On Fri, 25 Sep 2009 13:37:47 BST, "Dr. David Alan Gilbert" said:
>
> > Given an fd opened in this way is it possible to reopen it normally and
> > be guarenteed to get the same object?
>
> It's not possible even without this flag. Consider:
>
> fd1 = open("/tmp/foo",flags);
> rc = rename("/tmp/foo","/tmp/bar");
> fd2 = open("/tmp/foo",flags);
>
> Or were you asking if *absent that sort of tomfoolery* if it would work?

No, the point is that we HAVE an fd that points to the original "/tmp/foo"
opened with O_NODE, and now (after an ioctl, stat, etc) we decide it is
safe to open the file read and/or write without releasing the existing
fd. The whole point is to AVOID this kind of tomfoolery.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

--
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/