Dave G. - how about checking to see if they're the same, if both are
set, and if they are, call only one?  But otherwise, call whatever is
set, which may be both?

I agree with you otherwise, though; I'd prefer to leave it as is.

-John

David Lehmann wrote:
David Grothe wrote:

David:

I think I see what is going on. Consider the following lines from the trace:
...
Queues come in pairs. This loop is examining each queue of the pair and calling the close routine for whichever queue has a pointer to a close routine. Apparently your qinfo structure for your module has a pointer to the close routine for both the read and write queues. It is conventional to only provide open/close routine pointers for the read queue.


I think if you change your qinit structure the problem will go away.


Maybe so, but this is the same code that Solaris uses.
My understanding is that close should be called once and only once
for the queue pair.  Maybe you should take John's suggestion and
set do_close to zero after executing the close routine once.



_______________________________________________
Linux-streams mailing list
[EMAIL PROTECTED]
http://gsyc.escet.urjc.es/mailman/listinfo/linux-streams

Reply via email to