[Bugs] [Bug 1335776] rpc: change client insecure port ceiling from 65535 to 49151

bugzilla at redhat.com bugzilla at redhat.com
Wed May 18 10:26:04 UTC 2016


https://bugzilla.redhat.com/show_bug.cgi?id=1335776



--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14326 committed in master by Raghavendra G
(rgowdapp at redhat.com) 
------
commit 58615482ed87ff4b8253081c6ea26471fcf09070
Author: Prasanna Kumar Kalever <prasanna.kalever at redhat.com>
Date:   Fri May 13 13:17:16 2016 +0530

    rpc: change client insecure port ceiling from 65535 to 49151

    current port allocation to various processes (clumsy):

     1023 - 1       -> client ports range if bind secure is turned on
    49151 - 1024    -> fall back to this, if in above case ports exhaust
    65535 - 1024    -> client port range if bind insecure is on
    49152 - 65535   -> brick port range

    now, we have segregated port ranges 0 - 65535 to below 3 ranges

     1023 - 1       -> client ports range if bind secure is turned on
    49151 - 1024    -> client port range if bind insecure is on
                       (fall back to this, if in above case ports exhaust)
    49152 - 65535   -> brick port range

    so now we have a clean segregation of port mapping

    Change-Id: Ie3b4e7703e0bbeabbe0adbdd6c60d9ef78ef7c65
    BUG: 1335776
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever at redhat.com>
    Reviewed-on: http://review.gluster.org/14326
    Tested-by: Prasanna Kumar Kalever <pkalever at redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur at redhat.com>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle at redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list