Hi!

I am hit by this annoying bug:
 
https://sourceforge.net/tracker/?func=detail&aid=3446148&group_id=12694&atid=112694

I am  trying to fix  this. The situation  seems quite simple. Here  is a
pseudo-trace:

 - snmp_async_send()
 - snmp_sess_async_send()
 - _sess_async_send()
 - snmpv3_engineID_probe()
 - sptr->probe_engineid() and sptr->post_probe_engineid()

Those two callbacks can be:
 - snmpv3_probe_contextEngineID_rfc5343()
 - usm_discover_engineid()
 - usm_create_user_from_session_hook()

The last one seems OK.

The two first ones  call snmp_sess_synch_response(). The problem is that
if  we want  to  fix  this, we  need  to change  the  semantics for  the
callbacks. Is  it OK  to change the  first callback  to an async  one? I
don't know if the semantics of the second one needs any adaptation.
-- 
Vincent Bernat ☯ http://vincent.bernat.im

printk("HPFS: Grrrr... Kernel memory corrupted ... going on, but 
        it'll crash very soon :-(\n");
        2.4.3 linux/fs/hpfs/super.c

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to