From: Nikolay Borisov <nborisov@suse.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] btrfs: remove btrfs_raid_bio::fs_info member
Date: Thu, 23 Sep 2021 11:53:10 +0300 [thread overview]
Message-ID: <bd85e5e2-4118-34ce-c080-ae0b04bd6fea@suse.com> (raw)
In-Reply-To: <20210923060009.53821-2-wqu@suse.com>
On 23.09.21 г. 9:00, Qu Wenruo wrote:
> We can grab fs_info reliably from btrfs_raid_bio::bioc, as the bioc is
> always passed into alloc_rbio(), and only get released when the raid bio
> is released.
>
> This patch will remove btrfs_raid_bio::fs_info member, and cleanup all
> the @fs_info parameters for alloc_rbio() callers.
>
> Signed-off-by: Qu Wenruo <wqu@suse.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
next prev parent reply other threads:[~2021-09-23 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 6:00 [PATCH 1/2] btrfs: make sure btrfs_io_context::fs_info is always initialized Qu Wenruo
2021-09-23 6:00 ` [PATCH 2/2] btrfs: remove btrfs_raid_bio::fs_info member Qu Wenruo
2021-09-23 8:53 ` Nikolay Borisov [this message]
2021-09-23 8:36 ` [PATCH 1/2] btrfs: make sure btrfs_io_context::fs_info is always initialized Nikolay Borisov
2021-09-23 21:12 ` 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=bd85e5e2-4118-34ce-c080-ae0b04bd6fea@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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