Skip to content
Snippets Groups Projects
  1. May 19, 2011
    • Randy Dunlap's avatar
      Create Documentation/security/, · d410fa4e
      Randy Dunlap authored
      move LSM-, credentials-, and keys-related files from Documentation/
        to Documentation/security/,
      add Documentation/security/00-INDEX, and
      update all occurrences of Documentation/<moved_file>
        to Documentation/security/<moved_file>.
      d410fa4e
  2. May 06, 2011
  3. Apr 04, 2011
  4. Mar 16, 2011
  5. Aug 12, 2010
    • Adrian Hunter's avatar
      mmc: add erase, secure erase, trim and secure trim operations · dfe86cba
      Adrian Hunter authored
      
      SD/MMC cards tend to support an erase operation.  In addition, eMMC v4.4
      cards can support secure erase, trim and secure trim operations that are
      all variants of the basic erase command.
      
      SD/MMC device attributes "erase_size" and "preferred_erase_size" have been
      added.
      
      "erase_size" is the minimum size, in bytes, of an erase operation.  For
      MMC, "erase_size" is the erase group size reported by the card.  Note that
      "erase_size" does not apply to trim or secure trim operations where the
      minimum size is always one 512 byte sector.  For SD, "erase_size" is 512
      if the card is block-addressed, 0 otherwise.
      
      SD/MMC cards can erase an arbitrarily large area up to and
      including the whole card.  When erasing a large area it may
      be desirable to do it in smaller chunks for three reasons:
      
          1. A single erase command will make all other I/O on the card
             wait.  This is not a problem if the whole card is being erased, but
             erasing one partition will make I/O for another partition on the
             same card wait for the duration of the erase - which could be a
             several minutes.
      
          2. To be able to inform the user of erase progress.
      
          3. The erase timeout becomes too large to be very useful.
             Because the erase timeout contains a margin which is multiplied by
             the size of the erase area, the value can end up being several
             minutes for large areas.
      
      "erase_size" is not the most efficient unit to erase (especially for SD
      where it is just one sector), hence "preferred_erase_size" provides a good
      chunk size for erasing large areas.
      
      For MMC, "preferred_erase_size" is the high-capacity erase size if a card
      specifies one, otherwise it is based on the capacity of the card.
      
      For SD, "preferred_erase_size" is the allocation unit size specified by
      the card.
      
      "preferred_erase_size" is in bytes.
      
      Signed-off-by: default avatarAdrian Hunter <adrian.hunter@nokia.com>
      Acked-by: default avatarJens Axboe <axboe@kernel.dk>
      Cc: Kyungmin Park <kmpark@infradead.org>
      Cc: Madhusudhan Chikkature <madhu.cr@ti.com>
      Cc: Christoph Hellwig <hch@lst.de>
      Cc: Ben Gardiner <bengardiner@nanometrics.ca>
      Cc: <linux-mmc@vger.kernel.org>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      dfe86cba
  6. Aug 11, 2010
  7. Jul 20, 2010
  8. May 14, 2010
  9. Aug 22, 2009
  10. Mar 30, 2009
  11. Nov 14, 2008
  12. Nov 12, 2008
  13. Oct 28, 2008
  14. Oct 16, 2008
  15. Aug 05, 2008
  16. Jul 28, 2008
  17. Jul 25, 2008
  18. Jul 23, 2008
  19. Apr 25, 2008
  20. Apr 20, 2008
  21. Apr 17, 2008
  22. Apr 11, 2008
  23. Mar 12, 2008
  24. Mar 07, 2008
  25. Feb 13, 2008
  26. Feb 09, 2008
  27. Feb 07, 2008
  28. Feb 03, 2008
  29. Nov 29, 2007
    • Pavel Emelyanov's avatar
      The namespaces compatibility list doc · 2868f89f
      Pavel Emelyanov authored
      
      People discuss how the namespaces are working/going-to-work together.
      
      Ted Ts'o proposed to create some document that describes what problems user
      may have when he/she creates some new namespace, but keeps others shared.
      I liked this idea, so here's the initial version of such a document with
      the problems I currently have in mind and can describe somewhat audibly -
      the "namespaces compatibility list".
      
      The Documentation/namespaces/ directory is about to contain more docs about
      the namespaces stuff.
      
      Thanks to Cedirc for notes and spell checks on the doc, to Daniel for
      additional info about IPC and User namespaces interaction and to Randy, who
      alluded me to using a spell checker before sending the documentation :)
      
      Signed-off-by: default avatarPavel Emelyanov <xemul@openvz.org>
      Cc: Randy Dunlap <randy.dunlap@oracle.com>
      Cc: Daniel Lezcano <dlezcano@fr.ibm.com>
      Cc: Theodore Tso <tytso@mit.edu>
      Cc: Cedric Le Goater <clg@fr.ibm.com>
      Cc: "Eric W. Biederman" <ebiederm@xmission.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      2868f89f
  30. Nov 19, 2007
  31. Oct 17, 2007
Loading