public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] UBIFS changes for 2.6.37
Date: Fri, 22 Oct 2010 09:47:10 +0300	[thread overview]
Message-ID: <20101022064710.1687.65936.sendpatchset@localhost.localdomain> (raw)

Hi Linus,

Please, pull the UBIFS tree.

The following changes since commit 2bfc96a127bc1cc94d26bfaa40159966064f9c8c:

  Linux 2.6.36-rc3 (2010-08-29 08:36:04 -0700)

are available in the git repository at:
  git://git.infradead.org/ubifs-2.6.git linux-next

Artem Bityutskiy (17):
      UBIFS: switch to RO mode after synchronizing
      UBIFS: do not treat ENOSPC specially
      UBIFS: fix assertion warning
      UBIFS: do not look up truncation nodes
      UBIFS: do not use key type in list_sort
      UBIFS: improve assertion in node comparison functions
      UBIFS: do not write rubbish into truncation scanning node
      UBIFS: mark unused key objects as invalid
      UBIFS: fix assertion warnings in comparison function
      UBIFS: introduce list sorting debugging checks
      UBIFS: improve error reporting when reading bad node
      UBIFS: introduce new flag for RO due to errors
      UBIFS: introduce new flags for RO mounts
      UBIFS: add a commentary about log recovery
      UBIFS: remove a bit of unneeded code
      UBIFS: do not forget to cancel timers
      UBIFS: do not allocate unneeded scan buffer

Steffen Sledz (1):
      UBIFS: avoid kernel error if ubifs superblock read fails

Vasiliy Kulikov (2):
      UBIFS: check return code of ubifs_lpt_lookup
      UBIFS: check return code of pnode_lookup

 fs/ubifs/commit.c     |    4 +-
 fs/ubifs/debug.c      |  156 +++++++++++++++++++++++++++++++++++++++++++++++++
 fs/ubifs/debug.h      |    4 +
 fs/ubifs/file.c       |    7 +-
 fs/ubifs/gc.c         |   82 +++++++++++++++++++-------
 fs/ubifs/io.c         |   20 ++++---
 fs/ubifs/journal.c    |    3 +-
 fs/ubifs/key.h        |   14 +++++
 fs/ubifs/log.c        |    6 +-
 fs/ubifs/lpt.c        |    7 ++-
 fs/ubifs/lpt_commit.c |    3 +
 fs/ubifs/master.c     |    3 +-
 fs/ubifs/misc.h       |    9 ++-
 fs/ubifs/recovery.c   |   11 ++--
 fs/ubifs/replay.c     |   20 ++----
 fs/ubifs/sb.c         |    9 +--
 fs/ubifs/scan.c       |    6 +-
 fs/ubifs/shrinker.c   |    2 +-
 fs/ubifs/super.c      |   80 ++++++++++++++-----------
 fs/ubifs/tnc.c        |    5 +-
 fs/ubifs/ubifs.h      |   23 +++++--
 21 files changed, 362 insertions(+), 112 deletions(-)

Thanks,
Artem.

                 reply	other threads:[~2010-10-22  6:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101022064710.1687.65936.sendpatchset@localhost.localdomain \
    --to=artem.bityutskiy@nokia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox