[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2640.1268899857@jrobl>
Date: Thu, 18 Mar 2010 17:10:57 +0900
From: "J. R. Okajima" <hooanon05@...oo.co.jp>
To: Valerie Aurora <vaurora@...hat.com>
Cc: Alexander Viro <viro@...iv.linux.org.uk>,
Miklos Szeredi <miklos@...redi.hu>,
Dmitry Monakhov <dmonakhov@...nvz.org>,
Jeff Layton <jlayton@...hat.com>,
Christoph Hellwig <hch@...radead.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] Show data flow for file copyup in unions
Valerie Aurora:
> I think what people will expect is that we copy up in that case. I
> can think of ways this can go wrong, but perhaps that should be an
> explicit requirement on the top-layer file system, that it can handle
> create/unlink() in a directory without write permission.
I am not sure such requirement is the right way.
How about delegating open() to keventd or some other workqueue which
will succeed to create files under a directory without write permission?
Of course, we should handle some error cases after creating a file.
J. R. Okajima
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists