1. 12 Apr, 2018 1 commit
  2. 11 Apr, 2018 7 commits
  3. 10 Apr, 2018 1 commit
  4. 09 Apr, 2018 2 commits
    • David Howells's avatar
      afs: Implement @sys substitution handling · 6f8880d8
      David Howells authored
      Implement the AFS feature by which @sys at the end of a pathname component
      may be substituted for one of a list of values, typically naming the
      operating system.  Up to 16 alternatives may be specified and these are
      tried in turn until one works.  Each network namespace has[*] a separate
      independent list.
      Upon creation of a new network namespace, the list of values is
      initialised[*] to a single OpenAFS-compatible string representing arch type
      plus "_linux26".  For example, on x86_64, the sysname is "amd64_linux26".
      [*] Or will, once network namespace support is finalised in kAFS.
      The list may be set by:
      	# for i in foo bar linux-x86_64; do echo $i; done >/proc/fs/afs/sysname
      for which separate writes to the same fd are amalgamated and applied on
      close.  The LF character may be used as a separator to specify multiple
      items in the same write() call.
      The list may be cleared by:
      	# echo >/proc/fs/afs/sysname
      and read by:
      	# cat /proc/fs/afs/sysname
      Signed-off-by: default avatarDavid Howells <dhowells@redhat.com>
    • Prakash, Prashanth's avatar
      cpuidle: Add definition of residency to sysfs documentation · 792ccb45
      Prakash, Prashanth authored
      Add definition of minimum residency to sysfs documentation and
      update the tree to include the residency sysfs entry.
      Signed-off-by: default avatarPrashanth Prakash <pprakash@codeaurora.org>
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
  5. 08 Apr, 2018 1 commit
    • Esben Haabendal's avatar
      net/fsl_pq_mdio: Allow explicit speficition of TBIPA address · 21481189
      Esben Haabendal authored
      This introduces a simpler and generic method for for finding (and mapping)
      the TBIPA register.
      Instead of relying of complicated logic for finding the TBIPA register
      address based on the MDIO or MII register block base
      address, which even in some cases relies on undocumented shadow registers,
      a second "reg" entry for the mdio bus devicetree node specifies the TBIPA
      Backwards compatibility is kept, as the existing logic is applied when
      only a single "reg" mapping is specified.
      Signed-off-by: default avatarEsben Haabendal <eha@deif.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  6. 07 Apr, 2018 1 commit
  7. 06 Apr, 2018 3 commits
  8. 04 Apr, 2018 13 commits
  9. 03 Apr, 2018 1 commit
    • Patrik Torstensson's avatar
      dm verity: add 'check_at_most_once' option to only validate hashes once · 843f38d3
      Patrik Torstensson authored
      This allows platforms that are CPU/memory contrained to verify data
      blocks only the first time they are read from the data device, rather
      than every time.  As such, it provides a reduced level of security
      because only offline tampering of the data device's content will be
      detected, not online tampering.
      Hash blocks are still verified each time they are read from the hash
      device, since verification of hash blocks is less performance critical
      than data blocks, and a hash block will not be verified any more after
      all the data blocks it covers have been verified anyway.
      This option introduces a bitset that is used to check if a block has
      been validated before or not.  A block can be validated more than once
      as there is no thread protection for the bitset.
      These changes were developed and tested on entry-level Android Go
      Signed-off-by: default avatarPatrik Torstensson <totte@google.com>
      Signed-off-by: default avatarMike Snitzer <snitzer@redhat.com>
  10. 02 Apr, 2018 5 commits
  11. 01 Apr, 2018 3 commits
    • Eric Dumazet's avatar
      inet: frags: break the 2GB limit for frags storage · 3e67f106
      Eric Dumazet authored
      Some users are willing to provision huge amounts of memory to be able
      to perform reassembly reasonnably well under pressure.
      Current memory tracking is using one atomic_t and integers.
      Switch to atomic_long_t so that 64bit arches can use more than 2GB,
      without any cost for 32bit arches.
      Note that this patch avoids an overflow error, if high_thresh was set
      to ~2GB, since this test in inet_frag_alloc() was never true :
      if (... || frag_mem_limit(nf) > nf->high_thresh)
      $ echo 16000000000 >/proc/sys/net/ipv4/ipfrag_high_thresh
      <frag DDOS>
      $ grep FRAG /proc/net/sockstat
      FRAG: inuse 14705885 memory 16000002880
      $ nstat -n ; sleep 1 ; nstat | grep Reas
      IpReasmReqds                    3317150            0.0
      IpReasmFails                    3317112            0.0
      Signed-off-by: default avatarEric Dumazet <edumazet@google.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    • Eric Dumazet's avatar
      inet: frags: use rhashtables for reassembly units · 648700f7
      Eric Dumazet authored
      Some applications still rely on IP fragmentation, and to be fair linux
      reassembly unit is not working under any serious load.
      It uses static hash tables of 1024 buckets, and up to 128 items per bucket (!!!)
      A work queue is supposed to garbage collect items when host is under memory
      pressure, and doing a hash rebuild, changing seed used in hash computations.
      This work queue blocks softirqs for up to 25 ms when doing a hash rebuild,
      occurring every 5 seconds if host is under fire.
      Then there is the problem of sharing this hash table for all netns.
      It is time to switch to rhashtables, and allocate one of them per netns
      to speedup netns dismantle, since this is a critical metric these days.
      Lookup is now using RCU. A followup patch will even remove
      the refcount hold/release left from prior implementation and save
      a couple of atomic operations.
      Before this patch, 16 cpus (16 RX queue NIC) could not handle more
      than 1 Mpps frags DDOS.
      After the patch, I reach 9 Mpps without any tuning, and can use up to 2GB
      of storage for the fragments (exact number depends on frags being evicted
      after timeout)
      $ grep FRAG /proc/net/sockstat
      FRAG: inuse 1966916 memory 2140004608
      A followup patch will change the limits for 64bit arches.
      Signed-off-by: default avatarEric Dumazet <edumazet@google.com>
      Cc: Kirill Tkhai <ktkhai@virtuozzo.com>
      Cc: Herbert Xu <herbert@gondor.apana.org.au>
      Cc: Florian Westphal <fw@strlen.de>
      Cc: Jesper Dangaard Brouer <brouer@redhat.com>
      Cc: Alexander Aring <alex.aring@gmail.com>
      Cc: Stefan Schmidt <stefan@osg.samsung.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    • Martin Blumenstingl's avatar
      dt-bindings: net: meson-dwmac: add support for the Meson8m2 SoC · a5af1fb9
      Martin Blumenstingl authored
      The Meson8m2 SoC uses a similar (potentially even identical) register
      layout for the dwmac glue as Meson8b and GXBB. Unfortunately there is no
      documentation available.
      Testing shows that both, RMII and RGMII PHYs are working if they are
      configured as on Meson8b. Add a new compatible string to the
      documentation so differences (if there are any) between Meson8m2 and the
      other SoCs can be taken care of within the driver.
      Signed-off-by: default avatarMartin Blumenstingl <martin.blumenstingl@googlemail.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  12. 30 Mar, 2018 2 commits
    • Bjorn Helgaas's avatar
      PCI/portdrv: Remove unnecessary "pcie_ports=auto" parameter · 4c0fd764
      Bjorn Helgaas authored
      The "pcie_ports=auto" parameter set pcie_ports_disabled and pcie_ports_auto
      to their compiled-in defaults, so specifying the parameter is the same as
      not using it at all.
      Remove the "pcie_ports=auto" parameter and update the documentation.
      Signed-off-by: default avatarBjorn Helgaas <bhelgaas@google.com>
    • Bjorn Helgaas's avatar
      PCI/portdrv: Remove "pcie_hp=nomsi" kernel parameter · 1e447c57
      Bjorn Helgaas authored
      7570a333 ("PCI: Add pcie_hp=nomsi to disable MSI/MSI-X for pciehp
      driver") added the "pcie_hp=nomsi" kernel parameter to work around this
      error on shutdown:
        irq 16: nobody cared (try booting with the "irqpoll" option)
        Pid: 1081, comm: reboot Not tainted 3.2.0 #1
        Disabling IRQ #16
      This happened on an unspecified system (possibly involving the Integrated
      Device Technology, Inc. Device 807f bridge) where "an un-wanted interrupt
      is generated when PCI driver switches from MSI/MSI-X to INTx while shutting
      down the device."
      The implication was that the device was buggy, but it is normal for a
      device to use INTx after MSI/MSI-X have been disabled.  The only problem
      was that the driver was still attached and it wasn't prepared for INTx
      interrupts.  Prarit Bhargava fixed this issue with fda78d7a ("PCI/MSI:
      Stop disabling MSI/MSI-X in pci_device_shutdown()").
      There is no automated way to set this parameter, so it's not very useful
      for distributions or end users.  It's really only useful for debugging, and
      we have "pci=nomsi" for that purpose.
      Revert 7570a333 to remove the "pcie_hp=nomsi" parameter.
      Signed-off-by: default avatarBjorn Helgaas <bhelgaas@google.com>
      Reviewed-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      CC: MUNEDA Takahiro <muneda.takahiro@jp.fujitsu.com>
      CC: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
      CC: Prarit Bhargava <prarit@redhat.com>