From: Jun Nie <jun.nie@linaro.org>
To: tytso@mit.edu, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: tudor.ambarus@linaro.org
Subject: [PATCH v2 0/2] optimize ea_inode block expansion to fix panic
Date: Tue, 3 Jan 2023 09:45:15 +0800 [thread overview]
Message-ID: <20230103014517.495275-1-jun.nie@linaro.org> (raw)
Optimize ea_inode block expansion to avoid memcpy if possible,
panic can be avoided in this way too.
Change vs version 1:
Only error and warning log format in patch 2 is modified per
Theodore's suggestion.
Jun Nie (2):
ext4: optimize ea_inode block expansion
ext4: refuse to create ea block when umounted
fs/ext4/xattr.c | 35 ++++++++++++++++++++++++-----------
1 file changed, 24 insertions(+), 11 deletions(-)
--
2.34.1
next reply other threads:[~2023-01-03 1:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 1:45 Jun Nie [this message]
2023-01-03 1:45 ` [PATCH v2 1/2] ext4: optimize ea_inode block expansion Jun Nie
2023-01-03 1:45 ` [PATCH v2 2/2] ext4: refuse to create ea block when umounted Jun Nie
2023-02-19 5:40 ` [PATCH v2 0/2] optimize ea_inode block expansion to fix panic Theodore Ts'o
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=20230103014517.495275-1-jun.nie@linaro.org \
--to=jun.nie@linaro.org \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=tytso@mit.edu \
/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®