All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: gregkh@linuxfoundation.org
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] UBIFS fixes for 4.19-rc4
Date: Fri, 21 Sep 2018 11:33:15 +0200	[thread overview]
Message-ID: <3383200.5o9oegka29@blindfold> (raw)

Greg,

The following changes since commit ae596de1a0c8c2c924dc99d23c026259372ab234:

  Compiler Attributes: naked can be shared (2018-09-20 15:23:58 +0200)

are available in the Git repository at:

  git://git.infradead.org/linux-ubifs.git tags/upstream-4.19-rc4

for you to fetch changes up to f061c1cc404a618858a77aea233fde0aeaad2f2d:

  Revert "ubifs: xattr: Don't operate on deleted inodes" (2018-09-20 21:37:41 +0200)

----------------------------------------------------------------
This pull request contains fixes for UBIFS:

- A wrong UBIFS assertion in mount code
- Fix for a NULL pointer deref in mount code
- Revert of a bad fix for xattrs

----------------------------------------------------------------
Richard Weinberger (2):
      ubifs: Check for name being NULL while mounting
      Revert "ubifs: xattr: Don't operate on deleted inodes"

Sascha Hauer (1):
      ubifs: drop false positive assertion

 fs/ubifs/super.c |  7 ++++++-
 fs/ubifs/xattr.c | 24 ------------------------
 2 files changed, 6 insertions(+), 25 deletions(-)

             reply	other threads:[~2018-09-21  9:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-21  9:33 Richard Weinberger [this message]
2018-09-21 13:53 ` [GIT PULL] UBIFS fixes for 4.19-rc4 Greg KH
2018-09-21 14:01   ` Richard Weinberger
2018-09-21 14:08     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2018-09-24  7:11 Peter Rosin
2018-09-24  7:19 ` Greg KH

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=3383200.5o9oegka29@blindfold \
    --to=richard@nod.at \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.