On Thu, 2007-11-29 at 08:47 -0800, Greg KH wrote: > On Thu, Nov 29, 2007 at 11:36:12AM -0500, Jon Masters wrote: > > On Wed, 2007-11-28 at 17:07 -0800, Greg KH wrote: > > > > > The easiest way is as Al described above, just have the userspace > > > program that wrote the file to disk, check it then. > > > > But the problem is that this isn't just Samba, this is a countless > > myriad of different applications. And if one of them doesn't support > > on-access scanning, then the whole solution isn't worth using. > > Ok, which specific applications do they care about? Last time I asked > it was still limited to a very small handful, all of which would be > trivial to add such a hook to.
Like I said, I'm trying to put together a set of "feature requirements" that we can publish to LKML and get feedback. I am lead to believe that they basically want to trap every file operation, of every potential userspace program, so I don't think it's a handful at this point. > > > There are some nice SAMBA plugins that do just that already out there... > > > > That's really not the problem :-) > > Yes it is. That's all you want to catch, when a Windows machine wants > to access a file on a SAMBA server. Do the check then, in userspace. Oh, I meant that if it was just Samba we'd all be home and dry by now. > Believe me, I've been over and over and over and over this before... Yeah. I know, I'm trying not to flog a dead horse here, but I think there's real genuine interest here this time around. So, maybe I'm just trying because everyone else already did, but it's worth a shot :-) Jon. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
