Hi Amos, Henrik.
Amos has already inform me about the main procedure for applying
bug-fix patches to trunk. But there are cases like this patch which fix
a problem which is not reported as bug(yet) but it is very possible to
cause problems. Moreover this is not problem only in squid-trunk but
must back-ported to squid3.1.
My question is which is the normal procedure about applying such
patches? Should I open a bug report about possible bug? I am just
applying the patch and you are deciding if it should be applied to
squid*-* branches?
Regards,
Christos
Christos Tsantilas wrote:
> ------------------------------------------------------------
> revno: 9462
> committer: Christos Tsantilas <chtsanti_at_users.sourceforge.net>
> branch nick: TRUNK
> timestamp: Wed 2009-01-28 20:02:36 +0200
> message:
> The idnsSentQueryVC function called as AsyncCall. There is the possibility
> when this function called the fd has start closing but not realy closed yet.
> In this case this function will try to do a comm_write (idnsDoSendQueryVC
> function) on sockect which closing and an assertion will triggered.
> An extra test needed here to test if the socket closing and if yes just return.
> modified:
> src/dns_internal.cc
>
Received on Wed Jan 28 2009 - 18:26:17 MST
This archive was generated by hypermail 2.2.0 : Thu Jan 29 2009 - 12:00:04 MST