All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Alasdair Kergon <agk@redhat.com>,
	Mike Snitzer <snitzer@kernel.org>,
	 Christoph Hellwig <hch@infradead.org>,
	Keith Busch <kbusch@kernel.org>,
	 Uday Shankar <ushankar@purestorage.com>
Cc: linux-block@vger.kernel.org, dm-devel@redhat.com,
	kernel test robot <lkp@intel.com>
Subject: Re: [dm-devel] [PATCH v3] blk-mq: enforce op-specific segment limits in blk_insert_cloned_request
Date: Thu, 02 Mar 2023 21:00:45 -0700	[thread overview]
Message-ID: <167781604577.209443.3783406495581654903.b4-ty@kernel.dk> (raw)
In-Reply-To: <20230301000655.48112-1-ushankar@purestorage.com>


On Tue, 28 Feb 2023 17:06:55 -0700, Uday Shankar wrote:
> The block layer might merge together discard requests up until the
> max_discard_segments limit is hit, but blk_insert_cloned_request checks
> the segment count against max_segments regardless of the req op. This
> can result in errors like the following when discards are issued through
> a DM device and max_discard_segments exceeds max_segments for the queue
> of the chosen underlying device.
> 
> [...]

Applied, thanks!

[1/1] blk-mq: enforce op-specific segment limits in blk_insert_cloned_request
      commit: 49d24398327e32265eccdeec4baeb5a6a609c0bd

Best regards,
-- 
Jens Axboe



--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel


WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: Alasdair Kergon <agk@redhat.com>,
	Mike Snitzer <snitzer@kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	Keith Busch <kbusch@kernel.org>,
	Uday Shankar <ushankar@purestorage.com>
Cc: linux-block@vger.kernel.org, dm-devel@redhat.com,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v3] blk-mq: enforce op-specific segment limits in blk_insert_cloned_request
Date: Thu, 02 Mar 2023 21:00:45 -0700	[thread overview]
Message-ID: <167781604577.209443.3783406495581654903.b4-ty@kernel.dk> (raw)
In-Reply-To: <20230301000655.48112-1-ushankar@purestorage.com>


On Tue, 28 Feb 2023 17:06:55 -0700, Uday Shankar wrote:
> The block layer might merge together discard requests up until the
> max_discard_segments limit is hit, but blk_insert_cloned_request checks
> the segment count against max_segments regardless of the req op. This
> can result in errors like the following when discards are issued through
> a DM device and max_discard_segments exceeds max_segments for the queue
> of the chosen underlying device.
> 
> [...]

Applied, thanks!

[1/1] blk-mq: enforce op-specific segment limits in blk_insert_cloned_request
      commit: 49d24398327e32265eccdeec4baeb5a6a609c0bd

Best regards,
-- 
Jens Axboe




  parent reply	other threads:[~2023-03-03  4:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01  0:06 [dm-devel] [PATCH v3] blk-mq: enforce op-specific segment limits in blk_insert_cloned_request Uday Shankar
2023-03-01  0:06 ` Uday Shankar
2023-03-01  0:33 ` [dm-devel] " Keith Busch
2023-03-01  0:33   ` Keith Busch
2023-03-02  1:57 ` [dm-devel] " Ming Lei
2023-03-02  1:57   ` Ming Lei
2023-03-03  4:00 ` Jens Axboe [this message]
2023-03-03  4:00   ` 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=167781604577.209443.3783406495581654903.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=hch@infradead.org \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=snitzer@kernel.org \
    --cc=ushankar@purestorage.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.