1. 09 8月, 2016 3 次提交
  2. 12 6月, 2016 1 次提交
  3. 11 6月, 2016 1 次提交
  4. 30 1月, 2016 1 次提交
    • A
      ipv4: ipconfig: avoid unused ic_proto_used symbol · 52b79e2b
      Arnd Bergmann 提交于
      When CONFIG_PROC_FS, CONFIG_IP_PNP_BOOTP, CONFIG_IP_PNP_DHCP and
      CONFIG_IP_PNP_RARP are all disabled, we get a warning about the
      ic_proto_used variable being unused:
      
      net/ipv4/ipconfig.c:146:12: error: 'ic_proto_used' defined but not used [-Werror=unused-variable]
      
      This avoids the warning, by making the definition conditional on
      whether a dynamic IP configuration protocol is configured. If not,
      we know that the value is always zero, so we can optimize away the
      variable and all code that depends on it.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      52b79e2b
  5. 25 11月, 2015 1 次提交
    • G
      net/ipv4/ipconfig: Rejoin broken lines in console output · 6c1c36b0
      Geert Uytterhoeven 提交于
      Commit 09605cc1 ("net ipv4: use preferred log methods") replaced
      a few calls of pr_cont() after a console print without a trailing
      newline by pr_info(), causing lines to be split during IP
      autoconfiguration, like:
      
          .
          ,
           OK
          IP-Config: Got DHCP answer from 192.168.97.254,
          my address is 192.168.97.44
      
      Convert these back to using pr_cont(), so it prints again:
      
          ., OK
          IP-Config: Got DHCP answer from 192.168.97.254, my address is 192.168.97.44
      
      Absorb the printing of "my address ..." into the previous call to
      pr_info(), as there's no reason to use a continuation there.
      
      Convert one more pr_info() to print nameservers while we're at it.
      
      Fixes: 09605cc1 ("net ipv4: use preferred log methods")
      Signed-off-by: NGeert Uytterhoeven <geert+renesas@glider.be>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6c1c36b0
  6. 19 11月, 2015 1 次提交
  7. 19 10月, 2015 1 次提交
    • L
      ipconfig: send Client-identifier in DHCP requests · 26fb342c
      Li RongQing 提交于
      A dhcp server may provide parameters to a client from a pool of IP
      addresses and using a shared rootfs, or provide a specific set of
      parameters for a specific client, usually using the MAC address to
      identify each client individually. The dhcp protocol also specifies
      a client-id field which can be used to determine the correct
      parameters to supply when no MAC address is available. There is
      currently no way to tell the kernel to supply a specific client-id,
      only the userspace dhcp clients support this feature, but this can
      not be used when the network is needed before userspace is available
      such as when the root filesystem is on NFS.
      
      This patch is to be able to do something like "ip=dhcp,client_id_type,
      client_id_value", as a kernel parameter to enable the kernel to
      identify itself to the server.
      Signed-off-by: NLi RongQing <roy.qing.li@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      26fb342c
  8. 13 8月, 2015 1 次提交
    • M
      net: ipv4: increase dhcp inter device timeout · 76550786
      Mugunthan V N 提交于
      When a system has multiple ethernet devices and during DHCP
      request (for using NFS), the system waits only for HZ/2 which is
      500mS before switching to another interface for DHCP.
      
      There are some routers (Ex: Trendnet routers) which responds to
      DHCP request at about 560mS. When the system has only one
      ethernet interface there is no issue as the timeout is 2S and the
      dev xid doesn't changes and only retries.
      
      But when the system has multiple Ethernet like DRA74x with CPSW
      in dual EMAC mode, the DHCP response is dropped as the dev xid
      changes while shifting to the next device. So changing inter
      device timeout to HZ (which is 1S).
      Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      76550786
  9. 04 4月, 2015 1 次提交
  10. 20 1月, 2015 1 次提交
    • F
      net: ipv4: handle DSA enabled master network devices · 728c0208
      Florian Fainelli 提交于
      The logic to configure a network interface for kernel IP
      auto-configuration is very simplistic, and does not handle the case
      where a device is stacked onto another such as with DSA. This causes the
      kernel not to open and configure the master network device in a DSA
      switch tree, and therefore slave network devices using this master
      network devices as conduit device cannot be open.
      
      This restriction comes from a check in net/dsa/slave.c, which is
      basically checking the master netdev flags for IFF_UP and returns
      -ENETDOWN if it is not the case.
      
      Automatically bringing-up DSA master network devices allows DSA slave
      network devices to be used as valid interfaces for e.g: NFS root booting
      by allowing kernel IP autoconfiguration to succeed on these interfaces.
      
      On the reverse path, make sure we do not attempt to close a DSA-enabled
      device as this would implicitely prevent the slave DSA network device
      from operating.
      Signed-off-by: NFlorian Fainelli <f.fainelli@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      728c0208
  11. 05 11月, 2014 1 次提交
  12. 28 10月, 2014 1 次提交
  13. 23 8月, 2014 1 次提交
  14. 10 7月, 2014 2 次提交
  15. 09 7月, 2014 1 次提交
  16. 14 2月, 2014 1 次提交
  17. 03 4月, 2013 1 次提交
    • P
      ipconfig: add informative timeout messages while waiting for carrier · 5e404cd6
      Paul Gortmaker 提交于
      Commit 3fb72f1e ("ipconfig wait
      for carrier") added a "wait for carrier on at least one interface"
      policy, with a worst case maximum wait of two minutes.
      
      However, if you encounter this, you won't get any feedback from
      the console as to the nature of what is going on.  You just see
      the booting process hang for two minutes and then continue.
      
      Here we add a message so the user knows what is going on, and
      hence can take action to rectify the situation (e.g. fix network
      cable or whatever.)  After the 1st 10s pause, output now begins
      that looks like this:
      
      	Waiting up to 110 more seconds for network.
      	Waiting up to 100 more seconds for network.
      	Waiting up to 90 more seconds for network.
      	Waiting up to 80 more seconds for network.
      	...
      
      Since most systems will have no problem getting link/carrier in the
      1st 10s, the only people who will see these messages are people with
      genuine issues that need to be resolved.
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      5e404cd6
  18. 21 3月, 2013 1 次提交
    • M
      ipconfig: Fix newline handling in log message. · 283951f9
      Martin Fuzzey 提交于
      When using ipconfig the logs currently look like:
      
      Single name server:
      [    3.467270] IP-Config: Complete:
      [    3.470613]      device=eth0, hwaddr=ac:de:48:00:00:01, ipaddr=172.16.42.2, mask=255.255.255.0, gw=172.16.42.1
      [    3.480670]      host=infigo-1, domain=, nis-domain=(none)
      [    3.486166]      bootserver=172.16.42.1, rootserver=172.16.42.1, rootpath=
      [    3.492910]      nameserver0=172.16.42.1[    3.496853] ALSA device list:
      
      Three name servers:
      [    3.496949] IP-Config: Complete:
      [    3.500293]      device=eth0, hwaddr=ac:de:48:00:00:01, ipaddr=172.16.42.2, mask=255.255.255.0, gw=172.16.42.1
      [    3.510367]      host=infigo-1, domain=, nis-domain=(none)
      [    3.515864]      bootserver=172.16.42.1, rootserver=172.16.42.1, rootpath=
      [    3.522635]      nameserver0=172.16.42.1, nameserver1=172.16.42.100
      [    3.529149] , nameserver2=172.16.42.200
      
      Fix newline handling for these cases
      Signed-off-by: NMartin Fuzzey <mfuzzey@parkeon.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      283951f9
  19. 19 2月, 2013 1 次提交
  20. 05 1月, 2013 1 次提交
  21. 01 11月, 2012 1 次提交
  22. 26 9月, 2012 1 次提交
  23. 22 9月, 2012 1 次提交
  24. 20 5月, 2012 1 次提交
  25. 16 5月, 2012 2 次提交
  26. 16 4月, 2012 1 次提交
  27. 12 3月, 2012 1 次提交
    • J
      net: Convert printks to pr_<level> · 058bd4d2
      Joe Perches 提交于
      Use a more current kernel messaging style.
      
      Convert a printk block to print_hex_dump.
      Coalesce formats, align arguments.
      Use %s, __func__ instead of embedding function names.
      
      Some messages that were prefixed with <foo>_close are
      now prefixed with <foo>_fini.  Some ah4 and esp messages
      are now not prefixed with "ip ".
      
      The intent of this patch is to later add something like
        #define pr_fmt(fmt) "IPv4: " fmt.
      to standardize the output messages.
      
      Text size is trivially reduced. (x86-32 allyesconfig)
      
      $ size net/ipv4/built-in.o*
         text	   data	    bss	    dec	    hex	filename
       887888	  31558	 249696	1169142	 11d6f6	net/ipv4/built-in.o.new
       887934	  31558	 249800	1169292	 11d78c	net/ipv4/built-in.o.old
      Signed-off-by: NJoe Perches <joe@perches.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      058bd4d2
  28. 17 1月, 2012 1 次提交
  29. 21 12月, 2011 1 次提交
  30. 19 11月, 2011 1 次提交
    • H
      ipv4: Remove all uses of LL_ALLOCATED_SPACE · 66088243
      Herbert Xu 提交于
      ipv4: Remove all uses of LL_ALLOCATED_SPACE
      
      The macro LL_ALLOCATED_SPACE was ill-conceived.  It applies the
      alignment to the sum of needed_headroom and needed_tailroom.  As
      the amount that is then reserved for head room is needed_headroom
      with alignment, this means that the tail room left may be too small.
      
      This patch replaces all uses of LL_ALLOCATED_SPACE in net/ipv4
      with the macro LL_RESERVED_SPACE and direct reference to
      needed_tailroom.
      
      This also fixes the problem with needed_headroom changing between
      allocating the skb and reserving the head room.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      66088243
  31. 15 11月, 2011 1 次提交
  32. 01 11月, 2011 1 次提交
  33. 02 7月, 2011 1 次提交
  34. 22 6月, 2011 1 次提交
  35. 20 5月, 2011 1 次提交
    • M
      ipconfig wait for carrier · 3fb72f1e
      Micha Nelissen 提交于
      v3 -> v4: fix return boolean false instead of 0 for ic_is_init_dev
      
      Currently the ip auto configuration has a hardcoded delay of 1 second.
      When (ethernet) link takes longer to come up (e.g. more than 3 seconds),
      nfs root may not be found.
      
      Remove the hardcoded delay, and wait for carrier on at least one network
      device.
      Signed-off-by: NMicha Nelissen <micha@neli.hopto.org>
      Cc: David Miller <davem@davemloft.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      3fb72f1e
  36. 31 3月, 2011 1 次提交