mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-mtd <linux-mtd@lists.infradead.org>
Subject: [GIT PULL] UBI/UBIFS/JFFS2 changes for v5.5-rc1
Date: Sun, 1 Dec 2019 21:18:47 +0100 (CET)	[thread overview]
Message-ID: <1044415561.103245.1575231527451.JavaMail.zimbra@nod.at> (raw)

Linus,

The following changes since commit ec5385196779fb927e7d8d5bf31bef14d7ce98ed:

  Merge tag 'iommu-fixes-v5.4-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu (2019-11-17 11:27:44 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs.git tags/upstream-5.5-rc1

for you to fetch changes up to 6e78c01fde9023e0701f3af880c1fd9de6e4e8e3:

  Revert "jffs2: Fix possible null-pointer dereferences in jffs2_add_frag_to_fragtree()" (2019-11-29 11:29:58 +0100)

----------------------------------------------------------------
This pull request contains mostly fixes for UBI, UBIFS and JFFS2:

UBI:
- Fix a regression around producing a anchor PEB for fastmap.
  Due to a change in our locking fastmap was unable to produce
  fresh anchors an re-used the existing one a way to often.

UBIFS:
- Fixes for endianness. A few places blindly assumed little endian.
- Fix for a memory leak in the orphan code.
- Fix for a possible crash during a commit.
- Revert a wrong bugfix.

JFFS2:
- Revert a bad bugfix in (false positive from a code checking
  tool).

----------------------------------------------------------------
Ben Dooks (Codethink) (3):
      ubifs: Force prandom result to __le32
      ubifs: Fixed missed le64_to_cpu() in journal
      ubifs: Fix type of sup->hash_algo

Joel Stanley (1):
      Revert "jffs2: Fix possible null-pointer dereferences in jffs2_add_frag_to_fragtree()"

Richard Weinberger (2):
      ubifs: Remove obsolete TODO from dfs_file_write()
      Revert "ubifs: Fix memory leak bug in alloc_ubifs_info() error path"

Rishi Gupta (1):
      ubi: Fix warning static is not at beginning of declaration

Sascha Hauer (1):
      ubi: Fix producing anchor PEBs

Stefan Roese (1):
      ubi: Print skip_check in ubi_dump_vol_info()

Zhihao Cheng (2):
      ubifs: do_kill_orphans: Fix a memory leak bug
      ubifs: ubifs_tnc_start_commit: Fix OOB in layout_in_gaps

 drivers/mtd/ubi/debug.c      |  1 +
 drivers/mtd/ubi/fastmap-wl.c | 31 ++++++++++++++++++-------------
 drivers/mtd/ubi/fastmap.c    | 14 +++++---------
 drivers/mtd/ubi/ubi.h        |  8 +++++---
 drivers/mtd/ubi/wl.c         | 32 ++++++++++++++------------------
 drivers/mtd/ubi/wl.h         |  1 -
 fs/jffs2/nodelist.c          |  2 +-
 fs/ubifs/debug.c             | 12 ------------
 fs/ubifs/journal.c           |  4 ++--
 fs/ubifs/orphan.c            | 17 ++++++++++-------
 fs/ubifs/sb.c                |  2 +-
 fs/ubifs/super.c             |  4 +---
 fs/ubifs/tnc_commit.c        | 34 +++++++++++++++++++++++++++-------
 13 files changed, 85 insertions(+), 77 deletions(-)

             reply	other threads:[~2019-12-01 20:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-01 20:18 Richard Weinberger [this message]
2019-12-03  1:30 ` pr-tracker-bot

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=1044415561.103245.1575231527451.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.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

all inboxes | Powered by JetHome®