1. 28 Dec, 2018 1 commit
  2. 13 Dec, 2018 6 commits
  3. 20 Nov, 2018 1 commit
  4. 23 Oct, 2018 24 commits
  5. 13 Oct, 2018 1 commit
  6. 20 Sep, 2018 3 commits
  7. 24 Aug, 2018 1 commit
  8. 14 Aug, 2018 3 commits
    • Richard Weinberger's avatar
      ubifs: Set default assert action to read-only · 99a24e02
      Richard Weinberger authored
      Traditionally UBIFS just reported a failed assertion and moved on. The
      drawback is that users will notice UBIFS bugs when it is too late, most
      of the time when it is no longer about to mount. This makes bug hunting
      problematic since valuable information from failing asserts is long gone
      when UBIFS is dead. The other extreme, panic'ing on a failing assert is
      also not worthwhile, we want users and developers give a chance to
      collect as much debugging information as possible if UBIFS hits an
      assert. Therefore go for the third option, switch to read-only mode when
      an assert fails. That way UBIFS will not write possible bad data to the
      MTD and gives users the chance to collect debugging information.
      Signed-off-by: 's avatarRichard Weinberger <richard@nod.at>
    • Richard Weinberger's avatar
      ubifs: Allow setting assert action as mount parameter · c38c5a7f
      Richard Weinberger authored
      Expose our three options to userspace.
      Signed-off-by: 's avatarRichard Weinberger <richard@nod.at>
    • Richard Weinberger's avatar
      ubifs: Rework ubifs_assert() · 2e52eb74
      Richard Weinberger authored
      With having access to struct ubifs_info in ubifs_assert() we can
      give more information when an assert is failing.
      By using ubifs_err() we can tell which UBIFS instance failed.
      Also multiple actions can be taken now.
      We support:
       - report: This is what UBIFS did so far, just report the failure and go
       - read-only: Switch to read-only mode.
       - panic: shoot the kernel in the head.
      Signed-off-by: 's avatarRichard Weinberger <richard@nod.at>