All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: stable@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Damien Le Moal <dlemoal@kernel.org>,
	Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: [PATCH 0/3] Preserve the request order in the block layer
Date: Tue, 22 Apr 2025 13:51:44 +0200	[thread overview]
Message-ID: <2025042223-subsiding-parka-b064@gregkh> (raw)
In-Reply-To: <20250418175401.1936152-1-bvanassche@acm.org>

On Fri, Apr 18, 2025 at 10:53:58AM -0700, Bart Van Assche wrote:
> Hi Greg,
> 
> In kernel v6.10 the zoned storage approach was changed from zoned write
> locking to zone write plugging. Because of this change the block layer
> must preserve the request order. Hence this backport of Christoph's
> "don't reorder requests passed to ->queue_rqs" patch series. Please
> consider this patch series for inclusion in the 6.12 stable kernel.
> 
> See also https://lore.kernel.org/linux-block/20241113152050.157179-1-hch@lst.de/.

You sent this twice, right?  I'll grab this "second" version as I'm
guessing they were the same?

thanks,

greg k-h

  parent reply	other threads:[~2025-04-22 11:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18 17:53 [PATCH 0/3] Preserve the request order in the block layer Bart Van Assche
2025-04-18 17:53 ` [PATCH 1/3] block: remove rq_list_move Bart Van Assche
2025-04-19 11:47   ` Sasha Levin
2025-04-18 17:54 ` [PATCH 2/3] block: add a rq_list type Bart Van Assche
2025-04-19 11:47   ` Sasha Levin
2025-04-18 17:54 ` [PATCH 3/3] block: don't reorder requests in blk_add_rq_to_plug Bart Van Assche
2025-04-19 11:47   ` Sasha Levin
2025-04-22 11:51 ` Greg Kroah-Hartman [this message]
2025-05-04 17:14   ` [PATCH 0/3] Preserve the request order in the block layer Bart Van Assche

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=2025042223-subsiding-parka-b064@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bvanassche@acm.org \
    --cc=dlemoal@kernel.org \
    --cc=hch@lst.de \
    --cc=jaegeuk@kernel.org \
    --cc=stable@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 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.