Messages in this thread | | | Date | Fri, 25 Jun 2004 22:03:42 +0200 | From | Jörn Engel <> | Subject | Re: [PATCH] A generic_file_sendpage() |
| |
On Fri, 25 June 2004 20:46:11 +0100, viro@parcelfarce.linux.theplanet.co.uk wrote: > > > > One of my goals for 2.7 is to get rid of all users of struct file* in > > the various read-, write- and send-functions. Currently, there are > > four of them, you would introduce number five. > > And how, pray tell, are you going to do that on filesystems that keep > part of context in file->private_data?
Not sure. NFSv3 appears to be fixable, the only context is the UID, which happens to be stored in the inode as well. NFSv4 and cifs could be worse, I didn't look closely yet. smbfs accesses the dentry, which has similar effects, but should be fixable as well.
Do you know of any impossible cases?
Jörn
-- My second remark is that our intellectual powers are rather geared to master static relations and that our powers to visualize processes evolving in time are relatively poorly developed. -- Edsger W. Dijkstra - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |