On Fri, Jun 20, 2008 at 02:19:24PM -0400, Dan McDonald wrote:
> Consider this innocuous ::print
>
> > 0xffffffff9505c100::print ipsa_t
> {
> ipsa_next = 0
> ipsa_ptpn = 0xffffffff942dca98
> ipsa_linklock = 0xffffffff942dcaa0
> ipsa_freefunc = sadb_freeassoc
> ipsa_authkeydata = {
> sak_key = 0xffffffff90de9870
> sak_keylen = 0x14
> sak_keybits = 0xa0
> sak_algid = 0x3
> }
> ipsa_encrkeydata = {
> sak_key = 0xffffffff96437a60
> sak_keylen = 0x20
> sak_keybits = 0x100
> sak_algid = 0xc
> }
> ipsa_src_cid = 0
> ipsa_dst_cid = 0xffffffff964243a8
> ipsa_proxy_cid = 0 <-------- KEBE SAYS WTF?!? -------
> . . .
>
> I did this on S10u5's mdb, and Nevada's too. What's funny is that
> ipsa_proxy_cid was removed in S10u4, so why is it still printing in mdb?
> This throws off the rest of the structure, making it VERY VERY hard to debug
> possible IPsec SA corruption.
Try adding module`ipsa_t, where module is a module that uses the structure.
(ip?). You're getting the old version in genunix.
Cheers,
- jonathan
> Any clues are, as always, welcome. Also, please keep me in replies, as I'm
> not on this list.
>
> Thanks,
> Dan
> _______________________________________________
> mdb-discuss mailing list
> mdb-discuss at opensolaris.org
