From: hch <hch@lst.de>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: hch <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Anuj Gupta <anuj20.g@samsung.com>,
Kanchan Joshi <joshi.k@samsung.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH 3/6] block: don't call bio_uninit from bio_endio
Date: Thu, 4 Jul 2024 09:23:55 +0200 [thread overview]
Message-ID: <20240704072355.GA25826@lst.de> (raw)
In-Reply-To: <58763b5f-712d-4c42-b5f4-4064e99a4e40@wdc.com>
On Wed, Jul 03, 2024 at 09:50:08AM +0000, Johannes Thumshirn wrote:
> Can we have sth. like this on top to avoid the duplication?:
I hope I can just get rid of it over the next merge window or two.
Right now the only two offenders I've found are bcache and bcachefs,
so it might not be that much work.
next prev parent reply other threads:[~2024-07-04 7:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 15:10 more integrity cleanups v3 Christoph Hellwig
2024-07-02 15:10 ` [PATCH 1/6] block: split integrity support out of bio.h Christoph Hellwig
2024-07-03 9:28 ` Johannes Thumshirn
2024-07-02 15:10 ` [PATCH 2/6] block: also return bio_integrity_payload * from stubs Christoph Hellwig
2024-07-03 9:29 ` Johannes Thumshirn
2024-07-02 15:10 ` [PATCH 3/6] block: don't call bio_uninit from bio_endio Christoph Hellwig
2024-07-03 9:50 ` Johannes Thumshirn
2024-07-04 7:23 ` hch [this message]
2024-07-02 15:10 ` [PATCH 4/6] block: call bio_integrity_unmap_free_user from blk_rq_unmap_user Christoph Hellwig
2024-07-03 9:32 ` Johannes Thumshirn
2024-07-02 15:10 ` [PATCH 5/6] block: don't free submitter owned integrity payload on I/O completion Christoph Hellwig
2024-07-03 9:33 ` Johannes Thumshirn
2024-07-03 12:19 ` Kanchan Joshi
2024-07-02 15:10 ` [PATCH 6/6] block: don't free the integrity payload in bio_integrity_unmap_free_user Christoph Hellwig
2024-07-03 9:33 ` Johannes Thumshirn
2024-07-03 12:21 ` Kanchan Joshi
2024-07-03 2:18 ` more integrity cleanups v3 Martin K. Petersen
2024-07-03 16:21 ` 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=20240704072355.GA25826@lst.de \
--to=hch@lst.de \
--cc=Johannes.Thumshirn@wdc.com \
--cc=anuj20.g@samsung.com \
--cc=axboe@kernel.dk \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=martin.petersen@oracle.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).