Messages in this thread | | | Date | Sat, 15 Nov 2003 17:18:44 +0000 | From | viro@parcelfa ... | Subject | Re: seq_file and exporting dynamically allocated data |
| |
On Sat, Nov 15, 2003 at 10:38:33AM +0100, Harald Welte wrote: > that doesn't help. As I am aware, the seq_file structure is only > allocated in the seq_open() call. How does seq_open() know which > private data (i.e. hash table) to associate with struct file?
Why should seq_open() know that? Its caller does and it can set the damn thing to whatever it wants.
> The only moment I know which htable corresponds to a proc entry is at > the time where I call proc_net_create() [or a similar function]. So the > information would need to be associated with the dentry or whatever... > seq_file() is allocated way too late.
Wrong. - 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/
| |