During some parameter limit checking work, I ran into what I believe to
be an error in FreeBSD. (Albeit unlikely to be hit)
A setsockopt of the SO_LINGER field will cause strange results if
the value is set above 32767.
This is due to the fact that in struct socket, the so_linger field
is a sign
I think your patch is fine as is, Mike! Good find! Even though
so_linger cannot be negative, it is often convenient to use a signed
integer to store the value to avoid unexpected arithmatic results
when mixing with signed operations. My quick perusal does not show
any cases
Matthew Dillon wrote:
I think your patch is fine as is, Mike! Good find! Even though
so_linger cannot be negative, it is often convenient to use a signed
integer to store the value to avoid unexpected arithmatic results
when mixing with signed operations. My quick perusal does
Matthew Dillon wrote:
I think your patch is fine as is, Mike! Good find! Even though
so_linger cannot be negative, it is often convenient to use a signed
integer to store the value to avoid unexpected arithmatic results
when mixing with signed operations. My quick perusal does
I was going to wait till 5.0 released first but I could do it now
if you want.
-Matt
:
:Matthew Dillon wrote:
:> I think your patch is fine as is, Mike! Good find! Even though
:> so_linger cannot be negative, it is often convenient to use
Matthew Dillon wrote:
I was going to wait till 5.0 released first but I could do it now
if you want.
It would help the Java work but I don't know if it is critical to
be done "today" vs some short time in the future. (Depends on the
timing of the Java project and the wish to get JCK cer
6 matches
Mail list logo
