Linux-kernel mailing list archive 2000-02,: Re: init_special_inode in 2.3.35

# Re: init_special_inode in 2.3.35

David Grothe (dave@gcom.com)
Tue, 11 Jan 2000 08:43:51 -0600

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Jim Nance: "Re: Does a Trident 4DWave DX works with 2.3.38"
- Previous message: Jesse Pollard: "Re: time_t size: The year 2038 bug?"
- Maybe in reply to: David Grothe: "init_special_inode in 2.3.35"
- Next in thread: David Grothe: "Re: init_special_inode in 2.3.35"

Alexander Viro wrote:

> _All_ ->u is off-limits for any device code. It
> belongs to hosting filesystem and to nobody else.

If a driver needs to have a private structure that associates with each "real"
file (inode instance) then what is the recommended technique? Private hash
table on major/minor? What is the officially recommended technique here.

I obviously misunderstood that the generic_ip was like a private structure
pointer in a number of other kernel control structures, such as net_device.

-- Dave

-
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.tux.org/lkml/

- Next message: Jim Nance: "Re: Does a Trident 4DWave DX works with 2.3.38"
- Previous message: Jesse Pollard: "Re: time_t size: The year 2038 bug?"
- Maybe in reply to: David Grothe: "init_special_inode in 2.3.35"
- Next in thread: David Grothe: "Re: init_special_inode in 2.3.35"