From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Xi Wang <xi.wang@gmail.com>
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Andrei Pelinescu-Onciul <andrei@iptel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v2] sctp: fix incorrect overflow check on autoclose
Date: Fri, 16 Dec 2011 08:00:05 -0500 [thread overview]
Message-ID: <4EEB40D5.7030906@hp.com> (raw)
In-Reply-To: <0BF79838-C86F-4C3F-8D51-4223D579764C@gmail.com>
On 12/15/2011 05:13 PM, Xi Wang wrote:
> On Dec 15, 2011, at 4:07 PM, Vlad Yasevich wrote:
>> I think it would be better to keep this value in seconds and get rid
>> of division in the setsockopt code. We could then have a min and max
>> values where max value could be something like 2 days. I really don't
>> see an autoclose value that is bigger then that being very useful. In
>> fact, most of the time these values are very small as one wants to close
>> out idle associations.
>
> Now I start to think exposing a new sysctl option might be a little
> overkill since autoclose is often small.
>
> How about this?
>
> 1) Simply store autoclose in seconds in setsockopt.
>
> 2) Avoid overflow in associola.c.
>
> asoc->timeouts[SCTP_EVENT_TIMEOUT_AUTOCLOSE] =
> (sp->autoclose > MAX_SCHEDULE_TIMEOUT / HZ)
> ? MAX_SCHEDULE_TIMEOUT
> : (unsigned long)sp->autoclose * HZ;
>
> Or we could use INT_MAX instead of MAX_SCHEDULE_TIMEOUT if you want to
> keep that value consistent across 32/64 bits.
This would work as well. I do like the max configurable though as it
might be a nice feature, but the above code is exactly what I was
thinking about too.
-vlad
>
> - xi
>
next prev parent reply other threads:[~2011-12-16 13:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 1:24 [PATCH RESEND] sctp: fix incorrect overflow check on autoclose Xi Wang
2011-12-09 17:38 ` Vladislav Yasevich
2011-12-09 18:04 ` Xi Wang
2011-12-12 22:18 ` Vladislav Yasevich
2011-12-13 22:00 ` Xi Wang
2011-12-13 22:15 ` Vladislav Yasevich
2011-12-14 21:35 ` Xi Wang
2011-12-14 21:48 ` [PATCH v2] " Xi Wang
2011-12-15 21:07 ` Vlad Yasevich
2011-12-15 22:13 ` Xi Wang
2011-12-16 13:00 ` Vlad Yasevich [this message]
2011-12-16 22:25 ` Xi Wang
2011-12-16 22:44 ` [PATCH v3] " Xi Wang
2012-01-03 15:52 ` Vladislav Yasevich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EEB40D5.7030906@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=akpm@linux-foundation.org \
--cc=andrei@iptel.org \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xi.wang@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).