From: Jan Kara <jack@suse.cz>
To: Ye Bin <yebin10@huawei.com>
Cc: jack@suse.cz, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] ext2: fix race between setxattr and write back
Date: Wed, 16 Aug 2023 17:53:54 +0200 [thread overview]
Message-ID: <20230816155354.5dkicbptvrgcvnhy@quack3> (raw)
In-Reply-To: <20230815112612.221145-1-yebin10@huawei.com>
On Tue 15-08-23 19:26:08, Ye Bin wrote:
> Diff v2 vs v1:
> 1. Do not use reservation window when allocate block for xattr.
> 2. Remove BUG() in ext2_try_to_allocate_with_rsv().
Thanks! I did't a few smaller spelling fixups on commit but otherwise the
patches look good so I've added them to my tree.
Honza
>
> Ye Bin (4):
> ext2: remove ext2_new_block()
> ext2: introduce flag argument for ext2_new_blocks()
> ext2: fix race between setxattr and write back
> ext2: dump current reservation window info
>
> fs/ext2/balloc.c | 32 +++++++++++++++++---------------
> fs/ext2/ext2.h | 8 ++++++--
> fs/ext2/inode.c | 2 +-
> fs/ext2/xattr.c | 4 +++-
> 4 files changed, 27 insertions(+), 19 deletions(-)
>
> --
> 2.31.1
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2023-08-16 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 11:26 [PATCH v2 0/4] ext2: fix race between setxattr and write back Ye Bin
2023-08-15 11:26 ` [PATCH v2 1/4] ext2: remove ext2_new_block() Ye Bin
2023-08-15 11:26 ` [PATCH v2 2/4] ext2: introduce flag argument for ext2_new_blocks() Ye Bin
2023-08-15 11:26 ` [PATCH v2 3/4] ext2: fix race between setxattr and write back Ye Bin
2023-08-15 11:26 ` [PATCH v2 4/4] ext2: dump current reservation window info Ye Bin
2023-08-16 15:53 ` Jan Kara [this message]
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=20230816155354.5dkicbptvrgcvnhy@quack3 \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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