From: Ye Bin <yebin@huaweicloud.com>
To: tytso@mit.edu, adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, jack@suse.cz, Ye Bin <yebin10@huawei.com>
Subject: [PATCH v4 0/2] ext4: fix WARNING in ext4_update_inline_data
Date: Tue, 7 Mar 2023 09:52:51 +0800 [thread overview]
Message-ID: <20230307015253.2232062-1-yebin@huaweicloud.com> (raw)
From: Ye Bin <yebin10@huawei.com>
Diff v4 vs v3:
Change the first patch's changelog.
Diff v3 vs v2:
Remove set 'EXT4_STATE_MAY_INLINE_DATA' flag from ext4_find_inline_data_nolock()
Diff v2 vs v1:
Only update 'inline_off' when do extra expand.
Ye Bin (2):
ext4: remove set 'EXT4_STATE_MAY_INLINE_DATA' flag from
ext4_find_inline_data_nolock()
ext4: fix WARNING in ext4_update_inline_data
fs/ext4/inline.c | 1 -
fs/ext4/inode.c | 7 ++++++-
fs/ext4/xattr.c | 3 +++
3 files changed, 9 insertions(+), 2 deletions(-)
--
2.31.1
next reply other threads:[~2023-03-07 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 1:52 Ye Bin [this message]
2023-03-07 1:52 ` [PATCH v4 1/2] ext4: remove set 'EXT4_STATE_MAY_INLINE_DATA' flag from ext4_find_inline_data_nolock() Ye Bin
2023-03-07 1:52 ` [PATCH v4 2/2] ext4: fix WARNING in ext4_update_inline_data Ye Bin
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=20230307015253.2232062-1-yebin@huaweicloud.com \
--to=yebin@huaweicloud.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yebin10@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 NNTP newsgroup(s).