Re: change of inode->i_private to inode->u.generic_ip

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Le Tue, 25 Dec 2007 19:12:09 +0530,
"Manish Katiyar" <mkatiyar@xxxxxxxxx> a écrit :

> In kernel 2.6 there was a change of the union member field of inode
> structure . So code which used previously used inode->u.generic_ip to
> store its private information should use the new field
> inode->i_private. I found references some sites that this change was
> done primarily to reduce the VFS inode structure size.
> 
> Any other reasons of doing this ??

It's explained in the patch, at http://lkml.org/lkml/2006/7/2/168. The
reason is that everybody was using u.generic_ip, but nobody added more
fields to the union, so the union was useless. It's basically a
cleanup. Something kernel hackers can do because the Linux kernel
internal interface is not stable:
http://lxr.free-electrons.com/source/Documentation/stable_api_nonsense.txt.

Sincerly,

Thomas
-- 
Thomas Petazzoni, thomas.petazzoni@xxxxxxxx, http://thomas.enix.org
Jabber, thomas.petazzoni@xxxxxxxxx
Toulibre, http://www.toulibre.org - APRIL, http://www.april.org
Fingerprint : 0BE1 4CF3 CEA4 AC9D CC6E  1624 F653 CB30 98D3 F7A7

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux