All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Ming Lei <ming.lei@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org
Subject: Re: [PATCH 1/2] block: also check bio alignment for bio based drivers
Date: Fri, 5 Jul 2024 15:36:30 +0200	[thread overview]
Message-ID: <20240705133630.GA30748@lst.de> (raw)
In-Reply-To: <Zofzm6TRrOFb5iy9@fedora>

On Fri, Jul 05, 2024 at 09:22:35PM +0800, Ming Lei wrote:
> On Fri, Jul 05, 2024 at 02:56:50PM +0200, Christoph Hellwig wrote:
> > Extend the checks added in 0676c434a99b ("block: check bio alignment
> > in blk_mq_submit_bio") for blk-mq drivers to bio based drivers as
> > all the same reasons apply for them as well.
> 
> Do we have bio based driver which may re-configure logical block size?

nvme multipath can, and it looks drbd might be able to do so as well.

> If yes, is it enough to do so? Cause queue usage counter is only held
> during bio submission, and it won't cover the whole bio lifetime.

Yes.  But for me the prime intend here is not to prevent that, but
to ensure we actually have the damn sanity check for all drivers
instead of just a few and instead a gazillion more or less equivalent
open coded versions.

That doesn't mean we shouldn't look into actually holding q_usage_count
over the entire bio lifetime for bio based drivers, but that's a
separate project.

  reply	other threads:[~2024-07-05 13:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-05 12:56 extend the bio alignment check to bio based drivers Christoph Hellwig
2024-07-05 12:56 ` [PATCH 1/2] block: also check bio alignment for " Christoph Hellwig
2024-07-05 13:22   ` Ming Lei
2024-07-05 13:36     ` Christoph Hellwig [this message]
2024-07-09 13:50       ` Ming Lei
2024-07-10  5:53         ` Christoph Hellwig
2024-07-05 13:25   ` John Garry
2024-07-05 13:37     ` Christoph Hellwig
2024-07-05 12:56 ` [PATCH 2/2] brd: remove sector alignment checks Christoph Hellwig

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=20240705133630.GA30748@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.