We've recently had a report of a bug with the generation of
request IDs.  When this ID reaches the maximum value,
it wraps back to 0, which is interpreted as a failure to send
the packet.  This triggers a double free of the PDU, which
can cause the agent to crash.
   See the thread
      "glibc double free error on snmp_sess_close"
           on the coders list for details.


It doesn't happen very often, but is fairly simple to address.
Attached is a patch to fix this - not just for the Reqid (which
is where the original problem hit), but also for the other IDs.

Question:  is it worth applying this immediately so that
it can be included in the 5.5 release, or should we wait?

Dave

Attachment: id-wrap.patch
Description: Binary data

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to