From: Anand Jain <anand.jain@oracle.com>
To: xiakaixu1987@gmail.com, clm@fb.com, josef@toxicpanda.com,
dsterba@suse.com
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Kaixu Xia <kaixuxia@tencent.com>
Subject: Re: [PATCH v2] btrfs: return EAGAIN when receiving a pending signal in the defrag loops
Date: Wed, 18 Nov 2020 17:53:21 +0800 [thread overview]
Message-ID: <4d25ee0c-ba57-cd3f-7a6a-981a21c0967d@oracle.com> (raw)
In-Reply-To: <1605672156-29051-1-git-send-email-kaixuxia@tencent.com>
On 18/11/20 12:02 pm, xiakaixu1987@gmail.com wrote:
> From: Kaixu Xia <kaixuxia@tencent.com>
>
> The variable ret is overwritten by the following variable defrag_count.
> Actually the code should return EAGAIN when receiving a pending signal
> in the defrag loops.
>
> Reported-by: Tosk Robot <tencent_os_robot@tencent.com>
> Signed-off-by: Kaixu Xia <kaixuxia@tencent.com>
> ---
> v2
> -return EAGAIN instead of remove the EAGAIN error.
Sorry I might have missed in v1. Why was EAGAIN needed here?
Return of defrag_count rather makes sense to me as of now.
Thanks, Anand
>
> fs/btrfs/ioctl.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
> index 69a384145dc6..6f13db6d30bd 100644
> --- a/fs/btrfs/ioctl.c
> +++ b/fs/btrfs/ioctl.c
> @@ -1519,7 +1519,7 @@ int btrfs_defrag_file(struct inode *inode, struct file *file,
> if (btrfs_defrag_cancelled(fs_info)) {
> btrfs_debug(fs_info, "defrag_file cancelled");
> ret = -EAGAIN;
> - break;
> + goto out_ra;
> }
>
> if (!should_defrag_range(inode, (u64)i << PAGE_SHIFT,
>
next prev parent reply other threads:[~2020-11-18 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 4:02 [PATCH v2] btrfs: return EAGAIN when receiving a pending signal in the defrag loops xiakaixu1987
2020-11-18 9:53 ` Anand Jain [this message]
2020-11-23 19:17 ` David Sterba
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=4d25ee0c-ba57-cd3f-7a6a-981a21c0967d@oracle.com \
--to=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=kaixuxia@tencent.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiakaixu1987@gmail.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).