Re: How can the so_pcb field of a "socket_t" instance be accessed with KPI?
Re: How can the so_pcb field of a "socket_t" instance be accessed with KPI?
- Subject: Re: How can the so_pcb field of a "socket_t" instance be accessed with KPI?
- From: Stephane Sudre <email@hidden>
- Date: Fri, 9 Feb 2007 11:04:09 +0100
To check that it's not NULL before calling socket_data_inject_in. Since
it's going to cause a kernel panic.
I guess a better way to deal with this would be to wonder why the
so_pcb field is NULL before that.
The issue is that I haven't found any possible good explanation for
so_pcb to be NULL till now (and I have never been able to reproduce the
issue). And unfortunately, almost every socket KPI API is calling
socket_lock (that is going to kernel panic if so_pcb is NULL).
On 8 févr. 07, at 20:33, Vincent Lubet wrote:
Follow up question: why would you want to perform this check?
Vincent
On Feb 8, 2007, at 11:10 AM, Josh Graessley wrote:
You can not get to this field. It is considered private. The contents
a specific to the protocol of the socket created.
-josh
On Feb 8, 2007, at 3:21 AM, Stephane wrote:
I would like to check that the so_pcb field of a socket_t instance
is non NULL.
Since KPI obfuscates things, I'm looking for a method to access this
field with no success so far.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden