1. 02 Oct, 2018 1 commit
  2. 25 Mar, 2015 1 commit
    • Sheng Yong's avatar
      UBIFS: extend debug/message capabilities · 235c362b
      Sheng Yong authored
      
      In the case where we have more than one volumes on different UBI
      devices, it may be not that easy to tell which volume prints the
      messages.  Add ubi number and volume id in ubifs_msg/warn/error
      to help debug. These two values are passed by struct ubifs_info.
      
      For those where ubifs_info is not initialized yet, ubifs_* is
      replaced by pr_*. For those where ubifs_info is not avaliable,
      ubifs_info is passed to the calling function as a const parameter.
      
      The output looks like,
      
      [   95.444879] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 696
      [   95.484688] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "test1"
      [   95.484694] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
      [   95.484699] UBIFS (ubi0:1): FS size: 30220288 bytes (28 MiB, 238 LEBs), journal size 1523712 bytes (1 MiB, 12 LEBs)
      [   95.484703] UBIFS (ubi0:1): reserved for root: 1427378 bytes (1393 KiB)
      [   95.484709] UBIFS (ubi0:1): media format: w4/r0 (latest is w4/r0), UUID 40DFFC0E-70BE-4193-8905-F7D6DFE60B17, small LPT model
      [   95.489875] UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 699
      [   95.529713] UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "test2"
      [   95.529718] UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
      [   95.529724] UBIFS (ubi1:0): FS size: 19808256 bytes (18 MiB, 156 LEBs), journal size 1015809 bytes (0 MiB, 8 LEBs)
      [   95.529727] UBIFS (ubi1:0): reserved for root: 935592 bytes (913 KiB)
      [   95.529733] UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID EEB7779D-F419-4CA9-811B-831CAC7233D4, small LPT model
      
      [  954.264767] UBIFS error (ubi1:0 pid 756): ubifs_read_node: bad node type (255 but expected 6)
      [  954.367030] UBIFS error (ubi1:0 pid 756): ubifs_read_node: bad node at LEB 0:0, LEB mapping status 1
      Signed-off-by: default avatarSheng Yong <shengyong1@huawei.com>
      Signed-off-by: default avatarArtem Bityutskiy <artem.bityutskiy@linux.intel.com>
      235c362b
  3. 26 Oct, 2012 1 commit
  4. 31 Aug, 2012 2 commits
  5. 16 May, 2012 3 commits
  6. 03 May, 2012 1 commit
  7. 04 Jul, 2011 2 commits
    • Artem Bityutskiy's avatar
      UBIFS: introduce helper functions for debugging checks and tests · 2b1844a8
      Artem Bityutskiy authored
      
      This patch introduces helper functions for all debugging checks, so instead of
      doing
      
      if (!(ubifs_chk_flags & UBIFS_CHK_GEN))
      
      we now do
      
      if (!dbg_is_chk_gen(c))
      
      This is a preparation to further changes where the flags will go away, and
      we'll need to only change the helper functions, but the code which utilizes
      them won't be touched.
      
      At the same time this patch removes 'dbg_force_in_the_gaps()',
      'dbg_force_in_the_gaps_enabled()', and dbg_failure_mode helpers for
      consistency.
      Signed-off-by: default avatarArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      2b1844a8
    • Artem Bityutskiy's avatar
      UBIFS: use correct flags in lprops · 37662447
      Artem Bityutskiy authored
      
      The UBIFS lpt tree is in many aspects similar to the TNC tree, and we have
      similar flags for these trees. And by mistake we use the COW_ZNODE flag for
      LPT in some places, instead of the right flag COW_CNODE. And this works
      only because these two constants have the same value.
      
      This patch makes all the LPT code to use COW_CNODE and also changes COW_CNODE
      constant value to make sure we do not misuse the flags any more.
      Signed-off-by: default avatarArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      37662447
  8. 16 May, 2011 4 commits
  9. 24 Mar, 2011 1 commit
  10. 16 Mar, 2011 1 commit
    • Artem Bityutskiy's avatar
      UBIFS: allocate scanning buffer on demand · cd5f7485
      Artem Bityutskiy authored
      
      Instead of using pre-allocated 'c->dbg->buf' buffer in
      'scan_check_cb()', dynamically allocate it when needed. The intend
      is to get rid of the pre-allocated 'c->dbg->buf' buffer and save
      128KiB of RAM (or more if PEB size is larger). Indeed, currently we
      allocate this memory even if the user never enables any self-check,
      which is wasteful.
      Signed-off-by: default avatarArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      cd5f7485
  11. 15 Sep, 2009 2 commits
  12. 10 Sep, 2009 1 commit
    • Artem Bityutskiy's avatar
      UBIFS: do not print scary error messages needlessly · 348709ba
      Artem Bityutskiy authored
      
      At the moment UBIFS print large and scary error messages and
      flash dumps in case of nearly any corruption, even if it is
      a recoverable corruption. For example, if the master node is
      corrupted, ubifs_scan() prints error dumps, then UBIFS recovers
      just fine and goes on.
      
      This patch makes UBIFS print scary error messages only in
      real cases, which are not recoverable. It adds 'quiet' argument
      to the 'ubifs_scan()' function, so the caller may ask 'ubi_scan()'
      not to print error messages if the caller is able to do recovery.
      Signed-off-by: default avatarArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      Reviewed-by: default avatarAdrian Hunter <Adrian.Hunter@nokia.com>
      348709ba
  13. 26 Jan, 2009 2 commits
  14. 23 Dec, 2008 1 commit
  15. 03 Dec, 2008 1 commit
  16. 30 Sep, 2008 2 commits
  17. 15 Jul, 2008 1 commit