From: Christoph Hellwig <hch@infradead.org>
To: Praveen Kumar <kumarpraveen@linux.microsoft.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
axboe@kernel.dk
Subject: Re: [PATCH] blk-mq: export blk_mq_submit_bio symbol
Date: Thu, 9 Sep 2021 06:48:00 +0100 [thread overview]
Message-ID: <YTmgEAEx69PR/RMy@infradead.org> (raw)
In-Reply-To: <20210909053653.144360-1-kumarpraveen@linux.microsoft.com>
On Thu, Sep 09, 2021 at 11:06:53AM +0530, Praveen Kumar wrote:
> There are use-cases like replication where need to hook the blk I/O
> operations for devices and perform specific operation and fallback to
> its original I/O operations.
> Prior to v5.9 there was make_request_fn and then blk_mq_submit_bio
> exported apis, which provided infrastructure to drivers to develop these
> features. However in v5.10-rc1 with below commit the API was removed
> from the export list.
>
> Previous commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.10-rc1&id=681cc5e8667e8579a2da8fa4090c48a2d73fc3bb
>
> This patch exports the blk_mq_submit_bio symbol to provide flexibility
> to the drivers.
Please send your users of this "feature" to this list for inclusion
and we'll help you to massage them into a non-broken version.
And yes, you should have gotten the memo by now that we don't export
anything for out of tree modules.
next prev parent reply other threads:[~2021-09-09 5:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 5:36 [PATCH] blk-mq: export blk_mq_submit_bio symbol Praveen Kumar
2021-09-09 5:48 ` Christoph Hellwig [this message]
2021-09-10 11:54 ` Praveen Kumar
2021-09-09 16:16 ` Chaitanya Kulkarni
2021-09-13 4:24 ` Praveen Kumar
2021-09-13 6:09 ` Christoph Hellwig
2021-09-13 7:03 ` Praveen Kumar
2021-09-20 5:30 ` Prasad Muppana
2021-09-20 20:25 ` Chaitanya Kulkarni
2021-09-22 5:45 ` Prasad Muppana
2021-09-22 14:29 ` Jens Axboe
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=YTmgEAEx69PR/RMy@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=kumarpraveen@linux.microsoft.com \
--cc=linux-block@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).