1. 14 5月, 2012 1 次提交
  2. 10 1月, 2012 1 次提交
  3. 11 9月, 2011 2 次提交
    • B
      mtd: nand: rename NAND_USE_FLASH_BBT · bb9ebd4e
      Brian Norris 提交于
      Recall the recently added prefix requirements:
       * "NAND_" for flags in nand.h, used in nand_chip.options
       * "NAND_BBT_" for flags in bbm.h, used in nand_chip.bbt_options
              or in nand_bbt_descr.options
      
      Thus, I am changing NAND_USE_FLASH_BBT to NAND_BBT_USE_FLASH.
      
      Again, this flag is found in bbm.h and so should NOT be used in the
      "nand_chip.options" field.
      Signed-off-by: NBrian Norris <computersforpeace@gmail.com>
      Signed-off-by: NArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      bb9ebd4e
    • B
      mtd: nand: consolidate redundant flash-based BBT flags · a40f7341
      Brian Norris 提交于
      This patch works with the following three flags from two headers (nand.h
      and bbm.h):
        (1) NAND_USE_FLASH_BBT (nand.h)
        (2) NAND_USE_FLASH_BBT_NO_OOB (nand.h)
        (3) NAND_BBT_NO_OOB (bbm.h)
      
      These flags are all related and interdependent, yet they were in
      different headers. Flag (2) is simply the combination of (1) and (3) and
      can be eliminated.
      
      This patch accomplishes the following:
        * eliminate NAND_USE_FLASH_BBT_NO_OOB (i.e., flag (2))
        * move NAND_USE_FLASH_BBT (i.e., flag (1)) to bbm.h
      
      It's important to note that because (1) and (3) are now both found in
      bbm.h, they should NOT be used in the "nand_chip.options" field.
      
      I removed a small section from the mtdnand DocBook because it referes to
      NAND_USE_FLASH_BBT in nand.h, which has been moved to bbm.h.
      Signed-off-by: NBrian Norris <computersforpeace@gmail.com>
      Signed-off-by: NArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      a40f7341
  4. 25 5月, 2011 1 次提交
  5. 31 3月, 2011 1 次提交
  6. 12 3月, 2011 1 次提交
  7. 04 12月, 2010 2 次提交
  8. 25 10月, 2010 1 次提交
  9. 02 8月, 2010 1 次提交
  10. 10 5月, 2010 1 次提交
  11. 25 2月, 2010 2 次提交
  12. 01 12月, 2009 1 次提交
  13. 05 1月, 2009 1 次提交
    • R
      [MTD] [NAND] fix nandsim sched.h references · a5cce42f
      Randy Dunlap 提交于
      Fix sched.h references:
      
      build-r7149.out:/local/linsrc/linux-next-20081215/drivers/mtd/nand/nandsim.c:1326: error: dereferencing pointer to incomplete type
      build-r7149.out:/local/linsrc/linux-next-20081215/drivers/mtd/nand/nandsim.c:1326: error: 'PF_MEMALLOC' undeclared (first use in this function)
      build-r7149.out:/local/linsrc/linux-next-20081215/drivers/mtd/nand/nandsim.c:1328: error: dereferencing pointer to incomplete type
      build-r7149.out:/local/linsrc/linux-next-20081215/drivers/mtd/nand/nandsim.c:1335: error: dereferencing pointer to incomplete type
      build-r7149.out:/local/linsrc/linux-next-20081215/drivers/mtd/nand/nandsim.c:1335: error: 'PF_MEMALLOC' undeclared (first use in this function)
      build-r7149.out:make[4]: *** [drivers/mtd/nand/nandsim.o] Error 1
      Signed-off-by: NRandy Dunlap <randy.dunlap@oracle.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com>
      a5cce42f
  14. 10 12月, 2008 4 次提交
  15. 12 8月, 2008 1 次提交
  16. 01 8月, 2008 2 次提交
  17. 30 7月, 2008 1 次提交
  18. 06 6月, 2008 1 次提交
  19. 05 6月, 2008 4 次提交
  20. 03 2月, 2008 1 次提交
  21. 20 10月, 2007 1 次提交
  22. 06 9月, 2007 1 次提交
    • A
      [MTD] [NAND] nandsim: avoid deadlocking FS · 98b830d2
      Artem Bityutskiy 提交于
      Make nandsim use GFP_NOFS when allocating memory, because it might
      be used by a file-system (e.g. UBIFS2) which means, if we are short
      of memory, we may deadlock. Indee, UBIFS is holding a lock, writes
      to the media, reaches this place in NANDsim, kmalloc does not find
      the requested amount of RAM, calls memory shrinker, which decides
      to writeback inodes, calls FS, and it deadlocks on the lock which
      is already being held. Below is the UBIFS backtrace which
      demonstrates that:
      
      [<c03717dc>] __mutex_lock_slowpath+0xc8/0x2e6
      [<c0371a16>] mutex_lock+0x1c/0x1f
      [<f8b9d076>] reserve_space+0x3d/0xa9 [ubifs]
      [<f8b9d1bd>] make_one_reservation+0x2b/0x86 [ubifs]
      [<f8b9d3fc>] ubifs_jrn_write_block+0xda/0x12f [ubifs]
      [<f8b9ff3a>] ubifs_writepage+0x11d/0x1ec [ubifs]
      [<c015d6ab>] shrink_inactive_list+0x7fa/0x969
      [<c015d8c8>] shrink_zone+0xae/0x10c
      [<c015e3b4>] try_to_free_pages+0x159/0x251
      [<c015980a>] __alloc_pages+0x125/0x2f0
      [<c016ff6a>] cache_alloc_refill+0x380/0x6ba
      [<c01703f3>] __kmalloc+0x14f/0x157
      [<f885722a>] do_state_action+0xab7/0xc74 [nandsim]
      [<f885760c>] switch_state+0x225/0x402 [nandsim]
      [<f8857e7e>] ns_hwcontrol+0x3e2/0x620 [nandsim]
      [<f8862f53>] nand_command+0x2e/0x1a5 [nand]
      [<f8861ad8>] nand_write_page+0x4a/0x9a [nand]
      [<f88617b4>] nand_do_write_ops+0x1cf/0x343 [nand]
      [<f8861a70>] nand_write+0x88/0xa6 [nand]
      [<f8850b0e>] part_write+0x72/0x8b [mtd]
      [<f88e19c5>] ubi_io_write+0x189/0x29c [ubi]
      [<f88dfb98>] ubi_eba_write_leb+0xb6/0x699 [ubi]
      [<f88def93>] ubi_leb_write+0xe4/0xe9 [ubi]
      [<f8ba3b82>] ubifs_wbuf_write_nolock+0x333/0x4c9 [ubifs]
      [<f8b9d28c>] write_node+0x74/0x8e [ubifs]
      [<f8b9d422>] ubifs_jrn_write_block+0x100/0x12f [ubifs]
      [<f8b9ff3a>] ubifs_writepage+0x11d/0x1ec [ubifs]
      [<c0159e5b>] __writepage+0xb/0x26
      [<c015a318>] write_cache_pages+0x203/0x2d9
      [<c015a411>] generic_writepages+0x23/0x2d
      [<c015a452>] do_writepages+0x37/0x39
      [<c018e24a>] __writeback_single_inode+0x96/0x399
      [<c018e903>] sync_sb_inodes+0x1a3/0x274
      [<c018ebf3>] writeback_inodes+0xa6/0xd8
      [<c015a9dd>] background_writeout+0x86/0x9e
      [<c015ae9c>] pdflush+0xfb/0x1b6
      [<c01387d7>] kthread+0x37/0x59
      [<c0104dc3>] kernel_thread_helper+0x7/0x14
      
      The deadlock is funny because it starts in pdflush/writeback,
      and comes back to writeback, then deadlocks. It seems we should look
      carefully for other places in UBI and MTD and use GFP_NOFS instead
      of GFP_KERNEL.
      Caught-by: NAdrian Hunter <ext-adrian.hunter@nokia.com>
      Signed-off-by: NArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      Signed-off-by: NDavid Woodhouse <dwmw2@infradead.org>
      98b830d2
  23. 18 4月, 2007 4 次提交
  24. 08 12月, 2006 1 次提交
  25. 29 11月, 2006 1 次提交
  26. 21 10月, 2006 2 次提交