mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: linux-mtd@lists.infradead.org
Cc: david@sigma-star.at, richard@nod.at, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] Assorted UBIFS fixes
Date: Fri, 22 Jan 2021 22:22:25 +0100	[thread overview]
Message-ID: <20210122212229.17072-1-richard@nod.at> (raw)

I'm currently hunting down a filesystem corruption, while reviewing
various parts of UBIFS I've found some other bugs.
This patches fix these bugs. In another series I'll add a feature to
be able to remove stale fscrypt contexts and wrong directory size counters.

Richard Weinberger (4):
  ubifs: Correctly set inode size in ubifs_link()
  ubifs: Don't add fscrypt context to xattrs
  ubifs: Update directory size when creating whiteouts
  ubifs: Harden ubifs_jnl_write_inode()

 fs/ubifs/dir.c     | 31 ++++++++++++++++++++-----------
 fs/ubifs/journal.c |  6 +++++-
 fs/ubifs/ubifs.h   |  2 +-
 fs/ubifs/xattr.c   |  2 +-
 4 files changed, 27 insertions(+), 14 deletions(-)

-- 
2.26.2


             reply	other threads:[~2021-01-22 21:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 21:22 Richard Weinberger [this message]
2021-01-22 21:22 ` [PATCH 1/4] ubifs: Correctly set inode size in ubifs_link() Richard Weinberger
2021-01-23  2:35   ` Zhihao Cheng
2021-01-22 21:22 ` [PATCH 2/4] ubifs: Don't add fscrypt context to xattrs Richard Weinberger
2021-01-22 21:22 ` [PATCH 3/4] ubifs: Update directory size when creating whiteouts Richard Weinberger
2021-01-23  2:45   ` Zhihao Cheng
2021-01-23 10:05     ` Richard Weinberger
2021-01-25  1:05     ` Zhihao Cheng
2021-01-25  7:55       ` Richard Weinberger
2021-01-25  9:31         ` Zhihao Cheng
2021-01-22 21:22 ` [PATCH 4/4] ubifs: Harden ubifs_jnl_write_inode() Richard Weinberger

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=20210122212229.17072-1-richard@nod.at \
    --to=richard@nod.at \
    --cc=david@sigma-star.at \
    --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 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®