One other thing, quickly. Lis should never attempt to modify, or barely otherwise even use, an inode belonging to any other filesystem. Unless, of course, someone who doesn't understand this to be the intent changes the code to do otherwise.
Otherwise, the u.generic_ip field is used appropriately. We've known about this since LiS 2.8, at least, and I changed the code way back then to avoid using non-LiS inodes directly.
I have to tell you, Brian, I shudder to think what you're facing in terms of maintenance effort, if you're assuming that you'll have to patch the kernel just for things to work. But, that's not news to you that I feel that way, I'm sure. 8^)
-John
Brian F. G. Bidulock wrote:
John,
LiS attaches stream heads to the u.generic_ip pointer, which unfortunately is part of the file-specific union in the inode structure. If LiS attempts to attach a stream head to a real filesystem inode the way that Linux Fast-STREAMS is doing it, it will risk corrupting the real filesystem's file system specific data in the inode.
_______________________________________________ Linux-streams mailing list [EMAIL PROTECTED] http://gsyc.escet.urjc.es/mailman/listinfo/linux-streams
