netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dborkman@redhat.com
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org, vyasevich@gmail.com
Subject: Re: [PATCH net] net: sctp: fix permissions for rto_alpha and rto_beta knobs
Date: Sun, 15 Jun 2014 01:18:30 -0700 (PDT)	[thread overview]
Message-ID: <20140615.011830.1834645975843111936.davem@davemloft.net> (raw)
In-Reply-To: <1402786754-16807-1-git-send-email-dborkman@redhat.com>

From: Daniel Borkmann <dborkman@redhat.com>
Date: Sun, 15 Jun 2014 00:59:14 +0200

> Commit 3fd091e73b81 ("[SCTP]: Remove multiple levels of msecs
> to jiffies conversions.") has silently changed permissions for
> rto_alpha and rto_beta knobs from 0644 to 0444. The purpose of
> this was to discourage users from tweaking rto_alpha and
> rto_beta knobs in production environments since they are key
> to correctly compute rtt/srtt.
> 
> RFC4960 under section 6.3.1. RTO Calculation says regarding
> rto_alpha and rto_beta under rule C3 and C4:
 ...
> While it is discouraged to adjust rto_alpha and rto_beta
> and not further specified how to adjust them, the RFC also
> doesn't explicitly forbid it, but rather gives a RECOMMENDED
> default value (rto_alpha=3, rto_beta=2). We have a couple
> of users relying on the old permissions before they got
> changed. That said, if someone really has the urge to adjust
> them, we could allow it with a warning in the log.
> 
> Fixes: 3fd091e73b81 ("[SCTP]: Remove multiple levels of msecs to jiffies conversions.")
> Signed-off-by: Daniel Borkmann <dborkman@redhat.com>

This permission change seemed unintentional, and doesn't make
much sense anyways to me.

So I'm applying this, thanks Daniel.

      reply	other threads:[~2014-06-15  8:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14 22:59 [PATCH net] net: sctp: fix permissions for rto_alpha and rto_beta knobs Daniel Borkmann
2014-06-15  8:18 ` David Miller [this message]

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=20140615.011830.1834645975843111936.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dborkman@redhat.com \
    --cc=linux-sctp@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vyasevich@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).