From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stef Bon Subject: Re: Again:request for integration inotify in FUSE and fs like CIFS. Date: Sat, 19 Mar 2011 11:39:10 +0100 Message-ID: References: <20110319094926.GN22723@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-fsdevel@vger.kernel.org To: Al Viro Return-path: Received: from mail-iw0-f174.google.com ([209.85.214.174]:62744 "EHLO mail-iw0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751203Ab1CSKjL convert rfc822-to-8bit (ORCPT ); Sat, 19 Mar 2011 06:39:11 -0400 Received: by iwn34 with SMTP id 34so4835557iwn.19 for ; Sat, 19 Mar 2011 03:39:10 -0700 (PDT) In-Reply-To: <20110319094926.GN22723@ZenIV.linux.org.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 2011/3/19 Al Viro : >> >> I hope you get the picture, > > Why, yes, we do. =C2=A0You do not. =C2=A0It is up to you to implement= that; it is > up to us to decide whether the result is acceptable for merge... > OK, I see. I've posted here because there is other location for me to discuss this issue. I'm not that experienced in kernel develpment to just come with a merge right away. I needed some feedback to my idea. > FWIW, it's a bloody bad idea; inotify is not a generally usable mecha= nism. > There is no way to make it work for non-local filesystems. =C2=A0You = might be > able to hack up something in FUSE protocol; getting FUSE *servers* to > honour that is something entirely different, seeing that there are to= ns > of them and these codebases are not in any way under control of kerne= l > developers - or any single group, for that matter. =C2=A0Then there i= s NFS, > where even the protocol side of things is not up to us, not to mentio= n > the server implementations. =C2=A0The same goes for CIFS/SMB, only th= ere the > odds of affecting the protocol (or one of the common servers - you kn= ow, > the native Windows one) are even slimmer. That's right. I know it will not work always, the backend (or server) has to support it. With CIFS/SMB it's even more complicated then with FUSE. And with the tons of FUSE fs's, yes a lot of them will not use it, but that normal. A lot of them do not make use of Extended Attributes while it's possible, FUSE supports them. I only want very much inotify supported on the construction I'm working= on. > > Program relying on inotify is relying on specific configuration. =C2=A0= Namely, > the areas of the mount tree it's going to watch belonging to one of t= he > filesystems where inotify works. =C2=A0Depending on what you are tryi= ng to do > there might be saner (and more robust) ways to go - hard to tell with= out > knowing what are you trying to achieve. Well I'm building a construction where a FUSE fs play's an important ro= le. This FUSE fs (fuse-workspace) is basically an overlay fs, so the backend are filesystems on the same host, possibly mounted by the automounter. Well a userspace daemon is possible. There are already sollutions here, like gamin/fam. Any suggestions are welcome and appreciated. Stef Bon -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html