From: Zhihao Cheng <chengzhihao1@huawei.com>
To: <richard@nod.at>
Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<yi.zhang@huawei.com>
Subject: [PATCH 0/9] ubifs: Fix a serious of inconsistent problems when powercut happens
Date: Wed, 10 Apr 2024 15:37:42 +0800 [thread overview]
Message-ID: <20240410073751.2522830-1-chengzhihao1@huawei.com> (raw)
UBIFS is tolerant of powercut, this patchset fix some inconsistent
problems when powercut happens.
Xfstests,mtd-utils and powercut tests[1] are passed(Enable chk* debugging)
after this patchset applied.
[1] https://bugzilla.kernel.org/show_bug.cgi?id=218309
performance regression:
4GB nandsim 256KB PEB 4KB page
1. fio
direct=0
bs=4k
sync=0
iodepth=128
rw=write
iodepth_batch_complete=1
iodepth_batch=1
numjobs=1
directory=/root/temp
size=1G
runtime=20s
time_based=1
before after
1 thread seq write 412MiB/s 409MiB/s
1 thread random write 402MiB/s 397MiB/s
4 thread seq write 163MiB/s 164MiB/s
4 thread random write 162MiB/s 160MiB/s
2. fsmark
fs_mark -d /root/temp -s 10240 -n 1000
before after
7131 Files/sec 7090 Files/sec
Zhihao Cheng (9):
ubifs: Fix unattached xattr inode if powercut happens after deleting
ubifs: Don't add xattr inode into orphan area
Revert "ubifs: ubifs_symlink: Fix memleak of inode->i_link in error
path"
ubifs: Remove insert_dead_orphan from replaying orphan process
ubifs: Fix adding orphan entry twice for the same inode
ubifs: Move ui->data initialization after initializing security
ubifs: Fix space leak when powercut happens in linking tmpfile
ubifs: Fix unattached inode when powercut happens in creating
ubifs: dbg_orphan_check: Fix missed key type checking
fs/ubifs/dir.c | 91 +++++++++++++++-----------
fs/ubifs/journal.c | 14 +++-
fs/ubifs/orphan.c | 155 ++++++++-------------------------------------
fs/ubifs/ubifs.h | 7 +-
fs/ubifs/xattr.c | 2 +-
5 files changed, 92 insertions(+), 177 deletions(-)
--
2.39.2
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2024-04-10 7:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 7:37 Zhihao Cheng [this message]
2024-04-10 7:37 ` [PATCH 1/9] ubifs: Fix unattached xattr inode if powercut happens after deleting Zhihao Cheng
2024-04-10 7:37 ` [PATCH 2/9] ubifs: Don't add xattr inode into orphan area Zhihao Cheng
2024-04-10 7:37 ` [PATCH 3/9] Revert "ubifs: ubifs_symlink: Fix memleak of inode->i_link in error path" Zhihao Cheng
2024-04-10 7:37 ` [PATCH 4/9] ubifs: Remove insert_dead_orphan from replaying orphan process Zhihao Cheng
2024-04-10 7:37 ` [PATCH 5/9] ubifs: Fix adding orphan entry twice for the same inode Zhihao Cheng
2024-04-10 7:37 ` [PATCH 6/9] ubifs: Move ui->data initialization after initializing security Zhihao Cheng
2024-04-10 7:37 ` [PATCH 7/9] ubifs: Fix space leak when powercut happens in linking tmpfile Zhihao Cheng
2024-04-10 7:37 ` [PATCH 8/9] ubifs: Fix unattached inode when powercut happens in creating Zhihao Cheng
2024-04-10 7:37 ` [PATCH 9/9] ubifs: dbg_orphan_check: Fix missed key type checking Zhihao Cheng
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=20240410073751.2522830-1-chengzhihao1@huawei.com \
--to=chengzhihao1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=yi.zhang@huawei.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).