Re: Possible SCTP peer receive window bug

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi -

Jamie.Parsons (@UNKNOWN_DOMAIN :-() wrote:

> [...] There is still a bug in the system tap script as the exit
> value of functions is always returned as the same as the entry value
> to functions.  [...]

This is an occasionally confusing aspect of systemtap .return probes.
As per the stapprobes man page and elsewhere, most $context variables
accessed from .return probes represent function *entry-time snapshots*.

Try instead use of the @entry() construct, which makes explicit
which values you wish to be entry-time evaluated, and which later.

probe module("sctp").function("sctp_process_init").return {
     printf("sctp_process_init updates assoc %p peer rwnd to %d\n", 
     @entry($asoc), 
     @cast(@entry($asoc),"sctp_association")->peer->rwnd);
     /* evaluated at .return time:          ^^^^^^^^^^^^ */
}

(http://sourceware.org/PR14437 should make the @cast unnecessary
eventually.)

- FChE
--
To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Networking Development]     [Linux OMAP]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux