> I don't know of any other dependencies on inode fields, but I'll check
> further when I'm reviewing the network code. The i_flags usage is rather
> subtle, as it's buried in macros that look at the inode fields.
The question is not about networking side, but about VFS:
i.e. what fields any VFS user must initialize in order VFS
was happy.
Do you understand the point?
You add some new field to "struct inode" and all filesystems
(and networking) stop to work, because they do not know anything
about it. Well, now slowly repair all of them, and probably
after 30-40 patch levels all the things start to work again,
well only sysvfs is a bit broken.
Is it antiutopia? 8) Alas, it is reality.
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html