1. 04 5月, 2012 1 次提交
  2. 03 5月, 2012 10 次提交
  3. 01 5月, 2012 18 次提交
  4. 29 4月, 2012 5 次提交
  5. 27 4月, 2012 6 次提交
    • A
      tipc: Reject payload messages with invalid message type · aad58547
      Allan Stephens 提交于
      Adds check to ensure TIPC sockets reject incoming payload messages
      that have an unrecognized message type.
      
      Remove the old open question about whether TIPC_ERR_NO_PORT is
      the proper return value.  It is appropriate here since there are
      valid instances where another node can make use of the reply,
      and at this point in time the host is already broadcasting TIPC
      data, so there are no real security concerns.
      Signed-off-by: NAllan Stephens <allan.stephens@windriver.com>
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      aad58547
    • E
      net: cleanups in sock_setsockopt() · 82981930
      Eric Dumazet 提交于
      Use min_t()/max_t() macros, reformat two comments, use !!test_bit() to
      match !!sock_flag()
      Signed-off-by: NEric Dumazet <edumazet@google.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      82981930
    • H
      crush: include header for global symbols · feb50ac1
      hartleys 提交于
      Include the header to pickup the definitions of the global symbols.
      
      Quiets the following sparse warnings:
      
      warning: symbol 'crush_find_rule' was not declared. Should it be static?
      warning: symbol 'crush_do_rule' was not declared. Should it be static?
      Signed-off-by: NH Hartley Sweeten <hsweeten@visionengravers.com>
      Cc: Sage Weil <sage@newdream.net>
      Cc: "David S. Miller" <davem@davemloft.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      feb50ac1
    • E
      ipv6: RTAX_FEATURE_ALLFRAG causes inefficient TCP segment sizing · 67469601
      Eric Dumazet 提交于
      Quoting Tore Anderson from :
      https://bugzilla.kernel.org/show_bug.cgi?id=42572
      
      When RTAX_FEATURE_ALLFRAG is set on a route, the effective TCP segment
      size does not take into account the size of the IPv6 Fragmentation
      header that needs to be included in outbound packets, causing every
      transmitted TCP segment to be fragmented across two IPv6 packets, the
      latter of which will only contain 8 bytes of actual payload.
      
      RTAX_FEATURE_ALLFRAG is typically set on a route in response to
      receving a ICMPv6 Packet Too Big message indicating a Path MTU of less
      than 1280 bytes. 1280 bytes is the minimum IPv6 MTU, however ICMPv6
      PTBs with MTU < 1280 are still valid, in particular when an IPv6
      packet is sent to an IPv4 destination through a stateless translator.
      Any ICMPv4 Need To Fragment packets originated from the IPv4 part of
      the path will be translated to ICMPv6 PTB which may then indicate an
      MTU of less than 1280.
      
      The Linux kernel refuses to reduce the effective MTU to anything below
      1280 bytes, instead it sets it to exactly 1280 bytes, and
      RTAX_FEATURE_ALLFRAG is also set. However, the TCP segment size appears
      to be set to 1240 bytes (1280 Path MTU - 40 bytes of IPv6 header),
      instead of 1232 (additionally taking into account the 8 bytes required
      by the IPv6 Fragmentation extension header).
      
      This in turn results in rather inefficient transmission, as every
      transmitted TCP segment now is split in two fragments containing
      1232+8 bytes of payload.
      
      After this patch, all the outgoing packets that includes a
      Fragmentation header all are "atomic" or "non-fragmented" fragments,
      i.e., they both have Offset=0 and More Fragments=0.
      
      With help from David S. Miller
      Reported-by: NTore Anderson <tore@fud.no>
      Signed-off-by: NEric Dumazet <edumazet@google.com>
      Cc: Maciej Żenczykowski <maze@google.com>
      Cc: Tom Herbert <therbert@google.com>
      Tested-by: NTore Anderson <tore@fud.no>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      67469601
    • A
      tipc: Enhance error checking of published names · 8f177896
      Allan Stephens 提交于
      Consolidates validation of scope and name sequence range values into
      a single routine where it applies both to local name publications
      and to name publications issued by other nodes in the network. This
      change means that the scope value for non-local publications is now
      validated and the name sequence range for local publications is now
      validated only once. Additionally, a publication attempt that fails
      validation now creates an entry in the system log file only if debugging
      capabilities have been enabled; this prevents the system log from being
      cluttered up with messages caused by a defective application or network
      node.
      Signed-off-by: NAllan Stephens <allan.stephens@windriver.com>
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      8f177896
    • A
      tipc: Create helper routine to delete unused name sequence structure · f7fb9d20
      Allan Stephens 提交于
      Replaces two identical chunks of code that delete an unused name
      sequence structure from TIPC's name table with calls to a new routine
      that performs this operation.
      
      This change is cosmetic and doesn't impact the operation of TIPC.
      Signed-off-by: NAllan Stephens <allan.stephens@windriver.com>
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      f7fb9d20