1. 17 5月, 2012 1 次提交
  2. 29 2月, 2012 1 次提交
  3. 15 1月, 2012 1 次提交
  4. 13 1月, 2012 1 次提交
    • A
      UBIFS: fix key printing · 515315a1
      Artem Bityutskiy 提交于
      Before commit 56e46742 we have had locking
      around all printing macros and we could use static buffers for creating
      key strings and printing them. However, now we do not have that locking and
      we cannot use static buffers. This commit removes the old DBGKEY() macros
      and introduces few new helper macros for printing debugging messages plus
      a key at the end. Thankfully, all the messages are already structures in
      a way that the key is printed in the end.
      Signed-off-by: NArtem Bityutskiy <artem.bityutskiy@linux.intel.com>
      515315a1
  5. 12 1月, 2012 2 次提交
    • A
      UBIFS: fix debugging messages · d34315da
      Artem Bityutskiy 提交于
      Patch 56e46742 broke UBIFS debugging messages:
      before that commit when UBIFS debugging was enabled, users saw few useful
      debugging messages after mount. However, that patch turned 'dbg_msg()' into
      'pr_debug()', so to enable the debugging messages users have to enable them
      first via /sys/kernel/debug/dynamic_debug/control, which is very impractical.
      
      This commit makes 'dbg_msg()' to use 'printk()' instead of 'pr_debug()', just
      as it was before the breakage.
      Signed-off-by: NArtem Bityutskiy <artem.bityutskiy@linux.intel.com>
      Cc: stable@kernel.org [3.0+]
      d34315da
    • A
      UBIFS: make debugging messages light again · 1f5d78dc
      Artem Bityutskiy 提交于
      We switch to dynamic debugging in commit
      56e46742 but did not take into account that
      now we do not control anymore whether a specific message is enabled or not.
      So now we lock the "dbg_lock" and release it in every debugging macro, which
      make them not so light-weight.
      
      This commit removes the "dbg_lock" protection from the debugging macros to
      fix the issue.
      
      The downside is that now our DBGKEY() stuff is broken, but this is not
      critical at all and will be fixed later.
      Signed-off-by: NArtem Bityutskiy <artem.bityutskiy@linux.intel.com>
      Cc: stable@kernel.org [3.0+]
      1f5d78dc
  6. 22 8月, 2011 1 次提交
  7. 19 8月, 2011 1 次提交
  8. 04 7月, 2011 13 次提交
  9. 23 5月, 2011 1 次提交
    • A
      UBIFS: switch to dynamic printks · 56e46742
      Artem Bityutskiy 提交于
      Switch to debugging using dynamic printk (pr_debug()). There is no good reason
      to carry custom debugging prints if there is so cool and powerful generic
      dynamic printk infrastructure, see Documentation/dynamic-debug-howto.txt. With
      dynamic printks we can switch on/of individual prints, per-file, per-function
      and per format messages. This means that instead of doing old-fashioned
      
      echo 1 > /sys/module/ubifs/parameters/debug_msgs
      
      to enable general messages, we can do:
      
      echo 'format "UBIFS DBG gen" +ptlf' > control
      
      to enable general messages and additionally ask the dynamic printk
      infrastructure to print process ID, line number and function name. So there is
      no reason to keep UBIFS-specific crud if there is more powerful generic thing.
      Signed-off-by: NArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      56e46742
  10. 20 5月, 2011 1 次提交
  11. 14 5月, 2011 3 次提交
    • A
      UBIFS: dump the stack on errors in failure mode too · ec068142
      Artem Bityutskiy 提交于
      When UBIFS is in the failure mode (used for power cut emulation testing) we for
      some reasons do not dump the stack in many places, e.g., in assertions.
      Probably at early days we had too many of them and disabled this to make the
      development easier, but then never enabled. Nowadays I sometimes observe
      assertion failures during power cut testing, but the useful stackdump is not
      printed, which is bad. This patch makes UBIFS always print the stackdump when
      debugging is enabled.
      Signed-off-by: NArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      ec068142
    • A
      UBIFS: make force in-the-gaps to be a general self-check · bc3f07f0
      Artem Bityutskiy 提交于
      UBIFS can force itself to use the 'in-the-gaps' commit method - the last resort
      method which is normally invoced very very rarely. Currently this "force
      int-the-gaps" debugging feature is a separate test mode. But it is a bit saner
      to make it to be the "general" self-test check instead.
      
      This patch is just a clean-up which should make the debugging code look a bit
      nicer and easier to use - we have way too many debugging options.
      Signed-off-by: NArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      bc3f07f0
    • A
      UBIFS: improve space checking debugging feature · f1bd66af
      Artem Bityutskiy 提交于
      This patch improves the 'dbg_check_space_info()' function which checks
      whether the amount of space before re-mounting and after re-mounting
      is the same (remounting from R/O to R/W modes and vice-versa).
      
      The problem is that 'dbg_check_space_info()' does not save the budgeting
      information before re-mounting, so when an error is reported, we do not
      know why the amount of free space changed.
      
      This patches makes the following changes:
      
      1. Teaches 'dbg_dump_budg()' function to accept a 'struct ubifs_budg_info'
         argument and print out the this argument. This way we may ask it to
         print any saved budgeting info, no only the current one.
      2. Accordingly changes all the callers of 'dbg_dump_budg()' to comply with
         the changed interface.
      3. Introduce a 'saved_bi' (saved budgeting info) field to
         'struct ubifs_debug_info' and save the budgeting info before re-mounting
         there.
      4. Change 'dbg_check_space_info()' and make it print both old and new
         budgeting information.
      5. Additionally, save 'c->igx_gc_cnt' and print it if and error happens. This
         value contributes to the amount of free space, so we have to print it.
      Signed-off-by: NArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      f1bd66af
  12. 13 4月, 2011 1 次提交
  13. 16 3月, 2011 2 次提交
  14. 11 3月, 2011 1 次提交
  15. 30 8月, 2010 1 次提交
    • A
      UBIFS: introduce list sorting debugging checks · 3bb66b47
      Artem Bityutskiy 提交于
      The UBIFS bug in the GC list sorting comparison functions inspired
      me to write internal debugging check functions which verify that
      the list of nodes is sorted properly.
      
      So, this patch implements 2 new debugging functions:
       o 'dbg_check_data_nodes_order()' - check order of data nodes list
       o 'dbg_check_nondata_nodes_order()' - check order of non-data nodes list
      
      The debugging functions are executed only if general UBIFS debugging checks are
      enabled. And they are compiled out if UBIFS debugging is disabled.
      Signed-off-by: NArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      3bb66b47
  16. 15 9月, 2009 1 次提交
  17. 10 9月, 2009 1 次提交
  18. 26 1月, 2009 1 次提交
  19. 03 12月, 2008 3 次提交
  20. 30 9月, 2008 1 次提交
  21. 13 8月, 2008 1 次提交
  22. 15 7月, 2008 1 次提交