Re: dlil_output_list and interface filters
Re: dlil_output_list and interface filters
- Subject: Re: dlil_output_list and interface filters
- From: Josh Graessley <email@hidden>
- Date: Fri, 9 Jun 2006 13:06:22 -0700
That is definitely a bug. Please file a bug report. It does look like
this is fixed in the sources for the next major release (part of some
re-factoring), but it doesn't look like there were any changes made
for a software update fix.
Thanks,
-josh
On Jun 9, 2006, at 12:20 PM, Anton Kuzmin wrote:
I've been trying to nail down a mysterious kernel panic that occurs
when our KPI interface
filter is enabled and stumbled across a possible reason for it: in
dlil_output_list after a call
to filt_output, a check for EJUSTRETURN leads to what seems to be an
erroneous "continue",
which skips to the next interface filter instead of bailing out.
So basically any packet consumed by an interface filter still gets
passed to if_output and freed,
which leads to a nasty surprise for an unsuspecting filter still
referencing the freed mbuf.
Could someone do a sanity check on this and if it's indeed a bug,
I'll file a radar.
Also, I would be grateful if someone could explain why a failure to
process a single packet from
a list should cause freeing of the whole list.
Thanks,
Anton
_______________________________________________
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
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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