public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	 Mike Snitzer <snitzer@kernel.org>,
	linux-block@vger.kernel.org,  linux-scsi@vger.kernel.org
Subject: Re: fix stacking of sd-imposed max_sectors
Date: Tue, 28 May 2024 06:57:23 -0600	[thread overview]
Message-ID: <171690104393.274292.7885096310356049183.b4-ty@kernel.dk> (raw)
In-Reply-To: <20240523182618.602003-1-hch@lst.de>


On Thu, 23 May 2024 20:26:12 +0200, Christoph Hellwig wrote:
> this series fixes a regression in 6.10-rc report by Mike when using
> device mapper multipath on top of SCSI disks.  It is due the sd
> driver not only setting the hard max_dev_sectors limit but also
> pre-setting a potentially lower max_sectors value.
> 
> Diffstat:
>  block/blk-settings.c |    2 ++
>  drivers/scsi/sd.c    |    4 +++-
>  2 files changed, 5 insertions(+), 1 deletion(-)
> 
> [...]

Applied, thanks!

[1/2] sd: also set max_user_sectors when setting max_sectors
      commit: bafea1c58b24be594d97841ced1b7ae0347bf6e3
[2/2] block: stack max_user_sectors
      commit: e528bede6f4e6822afdf0fa80be46ea9199f0911

Best regards,
-- 
Jens Axboe




      parent reply	other threads:[~2024-05-28 12:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23 18:26 fix stacking of sd-imposed max_sectors Christoph Hellwig
2024-05-23 18:26 ` [PATCH 1/2] sd: also set max_user_sectors when setting max_sectors Christoph Hellwig
2024-05-23 18:53   ` Martin K. Petersen
2024-05-24  7:51     ` Christoph Hellwig
2024-05-23 18:26 ` [PATCH 2/2] block: stack max_user_sectors Christoph Hellwig
2024-05-23 18:54   ` Martin K. Petersen
2024-05-28 12:57 ` Jens Axboe [this message]

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=171690104393.274292.7885096310356049183.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=snitzer@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