From: Eric Sandeen <sandeen@redhat.com>
To: Andrey Utkin <andrey.krieger.utkin@gmail.com>, clm@fb.com, jbacik@fb.com
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] btrfs: Drop stray check of fixup_workers creation
Date: Sat, 09 Aug 2014 08:26:01 -0500 [thread overview]
Message-ID: <53E62169.1010905@redhat.com> (raw)
In-Reply-To: <1407585075-31035-1-git-send-email-andrey.krieger.utkin@gmail.com>
On 8/9/14, 6:51 AM, Andrey Utkin wrote:
> The issue was introduced in a79b7d4b3e8118f265dcb4bdf9a572c392f02708,
> adding allocation of extent_workers, so this stray check is surely not
> meant to be a check of something else.
>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=82021
> Reported-by: Maks Naumov <maksqwe1@ukr.net>
> Signed-off-by: Andrey Utkin <andrey.krieger.utkin@gmail.com>
Yup, harmless but unneeded.
However, might as well put the extent_workers & qgroup_rescan_workers checks
on the same line now...
Could probably do a V2 or fix it on commit, but anyway:
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
> ---
> fs/btrfs/disk-io.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> index 08e65e9..1881713 100644
> --- a/fs/btrfs/disk-io.c
> +++ b/fs/btrfs/disk-io.c
> @@ -2601,7 +2601,7 @@ int open_ctree(struct super_block *sb,
> fs_info->endio_freespace_worker && fs_info->rmw_workers &&
> fs_info->caching_workers && fs_info->readahead_workers &&
> fs_info->fixup_workers && fs_info->delayed_workers &&
> - fs_info->fixup_workers && fs_info->extent_workers &&
> + fs_info->extent_workers &&
> fs_info->qgroup_rescan_workers)) {
> err = -ENOMEM;
> goto fail_sb_buffer;
>
prev parent reply other threads:[~2014-08-09 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 11:51 [PATCH] btrfs: Drop stray check of fixup_workers creation Andrey Utkin
2014-08-09 13:26 ` Eric Sandeen [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=53E62169.1010905@redhat.com \
--to=sandeen@redhat.com \
--cc=andrey.krieger.utkin@gmail.com \
--cc=clm@fb.com \
--cc=jbacik@fb.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).