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 v3 0/4] Fix two issue about ext4 extended attribute
Date: Thu, 8 Dec 2022 10:32:29 +0800 [thread overview]
Message-ID: <20221208023233.1231330-1-yebin@huaweicloud.com> (raw)
From: Ye Bin <yebin10@huawei.com>
Diff v3 vs v2:
1. Remove patch [2-3].
2. Modify change log according to Bagas Sanjaya's suggestions.
Diff v2 vs v1:
1.Modify commit message about "ext4: fix WARNING in ext4_expand_extra_isize_ea"
2.Modify the indentation of arguments about "ext4: rename xattr_find_entry()
and __xattr_check_inode()"
This patchset fix two issues:
1. Patch [1]-[4] fix WARNING in ext4_expand_extra_isize_ea.
2. Patch [6] fix inode leak in 'ext4_xattr_inode_create()'.
3. Patch [5] is cleanup.
Ye Bin (4):
ext4: fix WARNING in ext4_expand_extra_isize_ea
ext4: allocate extended attribute value in vmalloc area
ext4: rename xattr_find_entry() and __xattr_check_inode()
ext4: fix inode leak in 'ext4_xattr_inode_create()'
fs/ext4/xattr.c | 42 +++++++++++++++++++++++-------------------
fs/ext4/xattr.h | 11 +++--------
2 files changed, 26 insertions(+), 27 deletions(-)
--
2.31.1
next reply other threads:[~2022-12-08 2:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 2:32 Ye Bin [this message]
2022-12-08 2:32 ` [PATCH v3 1/4] ext4: fix WARNING in ext4_expand_extra_isize_ea Ye Bin
2022-12-09 5:35 ` Theodore Ts'o
2022-12-08 2:32 ` [PATCH v3 2/4] ext4: allocate extended attribute value in vmalloc area Ye Bin
2022-12-09 5:35 ` Theodore Ts'o
2022-12-08 2:32 ` [PATCH v3 3/4] ext4: rename xattr_find_entry() and __xattr_check_inode() Ye Bin
2022-12-09 5:38 ` Theodore Ts'o
2022-12-08 2:32 ` [PATCH v3 4/4] ext4: fix inode leak in 'ext4_xattr_inode_create()' Ye Bin
2022-12-09 5:39 ` 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=20221208023233.1231330-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
all inboxes | Powered by JetHome®