From: Christoph Hellwig <hch@infradead.org>
To: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
Cc: Jens Axboe <abxoe@kernel.dk>,
Philipp Reisner <philipp.reisner@linbit.com>,
drbd-dev@lists.linbit.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
Lars Ellenberg <lars.ellenberg@linbit.com>,
stable@vger.kernel.org
Subject: Re: [RESEND PATCH] drbd: fix potential silent data corruption
Date: Wed, 30 Mar 2022 22:45:47 -0700 [thread overview]
Message-ID: <YkVACyO7rReUAjqj@infradead.org> (raw)
In-Reply-To: <20220330185551.3553196-1-christoph.boehmwalder@linbit.com>
The change looks good, but this really should grow a proper Fixes tag.
next prev parent reply other threads:[~2022-03-31 5:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 18:55 [RESEND PATCH] drbd: fix potential silent data corruption Christoph Böhmwalder
2022-03-31 5:45 ` Christoph Hellwig [this message]
2022-03-31 5:46 ` 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=YkVACyO7rReUAjqj@infradead.org \
--to=hch@infradead.org \
--cc=abxoe@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 \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox