linux-kernel - [GIT PULL] UBI/UBIFS changes for 2.6.39

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 07 Apr 2011 13:35:22 +0300
From:	Artem Bityutskiy <Artem.Bityutskiy@...ia.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Artem Bityutskiy <Artem.Bityutskiy@...ia.com>,
	linux-kernel@...r.kernel.org
Subject: [GIT PULL] UBI/UBIFS changes for 2.6.39

Hi Linus,

Please, pull the UBI and UBIFS fixes for 2.6.39.

The following changes since commit 0ce790e7d736cedc563e1fb4e998babf5a4dbc3d:

  Linux 2.6.39-rc1 (2011-03-29 12:09:47 -0700)

are available in the git repository at:
  git://git.infradead.org/ubifs-2.6.git for-linus

Artem Bityutskiy (10):
      UBIFS: do not read flash unnecessarily
      UBIFS: fix oops on error path in read_pnode
      UBIFS: fix assertion warnings
      UBIFS: do not select KALLSYMS_ALL
      UBIFS: unify error path dbg_debugfs_init_fs
      UBIFS: fix error path in dbg_debugfs_init_fs
      UBIFS: fix debugging failure in dbg_check_space_info
      UBI: check if we are in RO mode in the erase routine
      UBI: do not compare array with NULL
      UBI: do not select KALLSYMS_ALL

 drivers/mtd/ubi/Kconfig |    2 +-
 drivers/mtd/ubi/io.c    |    8 +++++-
 drivers/mtd/ubi/vmt.c   |    5 ---
 fs/ubifs/Kconfig        |    2 +-
 fs/ubifs/commit.c       |    2 +-
 fs/ubifs/debug.c        |   63 ++++++++++++++++++++++++++++++++++------------
 fs/ubifs/lpt.c          |    7 ++---
 fs/ubifs/super.c        |    3 +-
 8 files changed, 61 insertions(+), 31 deletions(-)

Thanks,
Artem.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/