1. 27 3月, 2012 1 次提交
  2. 11 1月, 2012 1 次提交
  3. 10 1月, 2012 5 次提交
  4. 25 10月, 2010 1 次提交
  5. 08 8月, 2010 1 次提交
  6. 20 5月, 2010 1 次提交
  7. 19 5月, 2010 2 次提交
  8. 09 7月, 2009 1 次提交
  9. 29 5月, 2009 1 次提交
  10. 10 12月, 2008 1 次提交
    • A
      [MTD] update internal API to support 64-bit device size · 69423d99
      Adrian Hunter 提交于
      MTD internal API presently uses 32-bit values to represent
      device size.  This patch updates them to 64-bits but leaves
      the external API unchanged.  Extending the external API
      is a separate issue for several reasons.  First, no one
      needs it at the moment.  Secondly, whether the implementation
      is done with IOCTLs, sysfs or both is still debated.  Thirdly
      external API changes require the internal API to be accepted
      first.
      
      Note that although the MTD API will be able to support 64-bit
      device sizes, existing drivers do not and are not required
      to do so, although NAND base has been updated.
      
      In general, changing from 32-bit to 64-bit values cause little
      or no changes to the majority of the code with the following
      exceptions:
          	- printk message formats
          	- division and modulus of 64-bit values
          	- NAND base support
      	- 32-bit local variables used by mtdpart and mtdconcat
      	- naughtily assuming one structure maps to another
      	in MEMERASE ioctl
      Signed-off-by: NAdrian Hunter <ext-adrian.hunter@nokia.com>
      Signed-off-by: NArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com>
      69423d99
  11. 12 8月, 2008 1 次提交
  12. 02 5月, 2008 2 次提交
  13. 23 4月, 2008 4 次提交
    • D
      [JFFS2] Add erase_checking_list to hold blocks being marked. · e2bc322b
      David Woodhouse 提交于
      Just to keep the debug code happy when it's adding all the blocks up.
      Otherwise, they disappear for a while while the locks are dropped to
      check them and write the cleanmarker.
      Signed-off-by: NDavid Woodhouse <dwmw2@infradead.org>
      e2bc322b
    • A
      [JFFS2] Return values of jffs2_block_check_erase error paths · 8a0f5723
      Anders Grafström 提交于
      It looks the error paths in jffs2_block_check_erase() have wrong return 
      values. A block that failed to be erased never gets marked as bad.
      Signed-off-by: NDavid Woodhouse <dwmw2@infradead.org>
      8a0f5723
    • D
      [JFFS2] Add paranoia debugging for superblock counts · 85a62db6
      David Woodhouse 提交于
      The problem fixed in commit 014b164e
      (space leak with in-band cleanmarkers) would have been caught a lot
      quicker if our paranoid debugging mode had included adding up the size
      counts from all the eraseblocks and comparing the totals with the counts
      in the superblock. Add that.
      
      Make jffs2_mark_erased_block() file the newly-erased block on the
      free_list before calling the debug function, to make it happy.
      Signed-off-by: NDavid Woodhouse <dwmw2@infradead.org>
      85a62db6
    • D
      [JFFS2] Fix free space leak with in-band cleanmarkers · 014b164e
      David Woodhouse 提交于
      We were accounting for the cleanmarker by calling jffs2_link_node_ref()
      (without locking!), which adjusted both superblock and per-eraseblock
      accounting, subtracting the size of the cleanmarker from {jeb,c}->free_size
      and adding it to {jeb,c}->used_size.
      
      But only _then_ were we adding the size of the newly-erased block back
      to the superblock counts, and we were adding each of jeb->{free,used}_size
      to the corresponding superblock counts. Thus, the size of the cleanmarker
      was effectively subtracted from the superblock's free_size _twice_.
      
      Fix this, by always adding a full eraseblock size to c->free_size when
      we've erased a block. And call jffs2_link_node_ref() under the proper
      lock, while we're at it.
      
      Thanks to Alexander Yurchenko and/or Damir Shayhutdinov for (almost)
      pinpointing the problem.
      Signed-off-by: NDavid Woodhouse <dwmw2@infradead.org>
      014b164e
  14. 22 4月, 2008 1 次提交
  15. 24 9月, 2007 1 次提交
  16. 22 8月, 2007 1 次提交
  17. 10 7月, 2007 1 次提交
  18. 29 6月, 2007 3 次提交
  19. 25 4月, 2007 1 次提交
    • D
      [JFFS2] Tidy up licensing/copyright boilerplate. · c00c310e
      David Woodhouse 提交于
      In particular, remove the bit in the LICENCE file about contacting
      Red Hat for alternative arrangements. Their errant IS department broke
      that arrangement a long time ago -- the policy of collecting copyright
      assignments from contributors came to an end when the plug was pulled on
      the servers hosting the project, without notice or reason.
      
      We do still dual-license it for use with eCos, with the GPL+exception
      licence approved by the FSF as being GPL-compatible. It's just that nobody
      has the right to license it differently.
      Signed-off-by: NDavid Woodhouse <dwmw2@infradead.org>
      c00c310e
  20. 18 4月, 2007 1 次提交
  21. 27 6月, 2006 2 次提交
  22. 27 5月, 2006 1 次提交
  23. 25 5月, 2006 2 次提交
  24. 24 5月, 2006 1 次提交
    • D
      [JFFS2] Reduce visibility of raw_node_ref to upper layers of JFFS2 code. · 2f785402
      David Woodhouse 提交于
      As the first step towards eliminating the ref->next_phys member and saving
      memory by using an _array_ of struct jffs2_raw_node_ref per eraseblock,
      stop the write functions from allocating their own refs; have them just
      _reserve_ the appropriate number instead. Then jffs2_link_node_ref() can
      just fill them in.
      
      Use a linked list of pre-allocated refs in the superblock, for now. Once
      we switch to an array, it'll just be a case of extending that array.
      Signed-off-by: NDavid Woodhouse <dwmw2@infradead.org>
      2f785402
  25. 22 5月, 2006 2 次提交
  26. 21 5月, 2006 1 次提交