From: Jan Kara <jack@suse.cz>
To: Coly Li <colyli@suse.de>
Cc: linux-bcache@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@infradead.org>,
<linux-block@vger.kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>,
Jan Kara <jack@suse.cz>
Subject: [PATCH v2 0/2] bcache: Fix block device claiming
Date: Thu, 22 Jun 2023 18:46:53 +0200 [thread overview]
Message-ID: <20230622164149.17134-1-jack@suse.cz> (raw)
Hello,
these two patches fix block device claiming for bcache broken by recent
Christoph's changes to blkdev_get_*() functions and also cleans up the layering
violation inside bcache which was the underlying cause of the breakage.
This time I've actually tested various modified error handling paths (which was
good because one of them was indeed wrong!).
Jens, please consider merging these fixes before sending Linus a pull request
with blkdev changes.
Changes since v1:
* Fix compile breakage spotted by 0-day
* Fix error handling path when the second blkdev_get_by_dev() fails
* Fix commit message of patch 2/2
Honza
Previous versions:
Link: http://lore.kernel.org/r/20230621162024.29310-1-jack@suse.cz # v1
next reply other threads:[~2023-06-22 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 16:46 Jan Kara [this message]
2023-06-22 16:46 ` [PATCH v2 1/2] bcache: Alloc holder object before async registration Jan Kara
2023-06-22 16:52 ` Kent Overstreet
2023-06-22 16:56 ` Coly Li
2023-06-22 16:46 ` [PATCH v2 2/2] bcache: Fix bcache device claiming Jan Kara
2023-06-22 16:52 ` Kent Overstreet
2023-06-22 16:55 ` Coly Li
2023-06-22 16:59 ` Coly Li
2023-06-23 22:10 ` [PATCH v2 0/2] bcache: Fix block " 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=20230622164149.17134-1-jack@suse.cz \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=colyli@suse.de \
--cc=hch@infradead.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@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