UBIFS updates for 2.6.27

[Artem Bityutskiy]

Hi,

here is the second bunch of UBIFS updates we would like to send to
Linus for 2.6.27 inclusion. The updates contain the following:

Adrian Hunter (2):
      UBIFS: always read hashed-key nodes under TNC mutex
      UBIFS: allow for racing between GC and TNC

Artem Bityutskiy (10):
      UBIFS: fix zero-length truncations
      UBIFS: do not update min_idx_lebs in stafs
      UBIFS: push empty flash hack down
      UBIFS: remove incorrect index space check
      UBIFS: improve statfs reporting
      UBIFS: fix assertion
      UBIFS: add forgotten gc_idx_lebs component
      UBIFS: introduce LEB overhead
      UBIFS: improve statfs reporting even more
      UBIFS: fill f_fsid

 fs/ubifs/budget.c |  113 +++++++++++++++++++++++++++++++++++++++------------
 fs/ubifs/dir.c    |    1 -
 fs/ubifs/file.c   |   20 +++++++--
 fs/ubifs/find.c   |   18 ++++-----
 fs/ubifs/gc.c     |    6 +++
 fs/ubifs/misc.h   |   49 ++++++++---------------
 fs/ubifs/super.c  |   19 +++++---
 fs/ubifs/tnc.c    |  116 ++++++++++++++++++++++++++++-------------------------
 fs/ubifs/ubifs.h  |   14 +++++-
 9 files changed, 217 insertions(+), 139 deletions(-)

These patches are pure fixes:
UBIFS: fix zero-length truncations
UBIFS: always read hashed-key nodes under TNC mutex
UBIFS: allow for racing between GC and TNC
UBIFS: fix assertion
UBIFS: add forgotten gc_idx_lebs component
UBIFS: remove incorrect index space check

These patches partially fix the problem reported in the MTD ML:
http://lists.infradead.org/pipermail/linux-mtd/2008-August/022579.html

UBIFS: do not update min_idx_lebs in stafs
UBIFS: push empty flash hack down
UBIFS: improve statfs reporting
UBIFS: introduce LEB overhead
UBIFS: improve statfs reporting even more

Thus, it should be fine to send them mainline at this late stage.
Unless there are complaints, I'll send a pull request soon.

Thanks.

-- 
Best regards,
Artem Bityutskiy (Ð?иÑ?Ñ?Ñ?кий Ð?Ñ?Ñ?Ñ?м)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/