Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
Cc: linux-block@vger.kernel.org,
	Lars Ellenberg <lars.ellenberg@linbit.com>,
	Philipp Reisner <philipp.reisner@linbit.com>,
	linux-kernel@vger.kernel.org, drbd-dev@lists.linbit.com
Subject: Re: [PATCH] drbd: always set BLK_FEAT_STABLE_WRITES
Date: Wed, 11 Feb 2026 10:36:20 -0700	[thread overview]
Message-ID: <177083138009.157276.14024749739595076725.b4-ty@kernel.dk> (raw)
In-Reply-To: <20260205173928.3166880-2-christoph.boehmwalder@linbit.com>


On Thu, 05 Feb 2026 18:39:29 +0100, Christoph Böhmwalder wrote:
> DRBD requires stable pages because it may read the same bio data
> multiple times for local disk I/O and network transmission, and in
> some cases for calculating checksums.
> 
> The BLK_FEAT_STABLE_WRITES flag is set when the device is first
> created, but blk_set_stacking_limits() clears it whenever a
> backing device is attached. In some cases the flag may be
> inherited from the backing device, but we want it to be enabled
> at all times.
> 
> [...]

Applied, thanks!

[1/1] drbd: always set BLK_FEAT_STABLE_WRITES
      commit: 2ebc8d600fb907fa6b1e7095c0b6d84fc47e91ea

Best regards,
-- 
Jens Axboe




      parent reply	other threads:[~2026-02-11 17:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 17:39 [PATCH] drbd: always set BLK_FEAT_STABLE_WRITES Christoph Böhmwalder
2026-02-06  6:43 ` Christoph Hellwig
2026-02-12 15:01   ` Christoph Böhmwalder
2026-02-13  6:05     ` Christoph Hellwig
2026-02-11 17:36 ` 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=177083138009.157276.14024749739595076725.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=christoph.boehmwalder@linbit.com \
    --cc=drbd-dev@lists.linbit.com \
    --cc=lars.ellenberg@linbit.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philipp.reisner@linbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox