From: Mike Snitzer <snitzer@redhat.com>
To: Sasha Levin <sashal@kernel.org>
Cc: John Donnelly <john.p.donnelly@oracle.com>,
stable@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: (resend) [PATCH [linux-4.14.y]] dm cache: submit writethrough writes in parallel to origin and cache
Date: Mon, 27 Jul 2020 16:30:26 -0400 [thread overview]
Message-ID: <20200727203025.GA28830@redhat.com> (raw)
In-Reply-To: <20200727201700.GJ406581@sasha-vm>
On Mon, Jul 27 2020 at 4:17pm -0400,
Sasha Levin <sashal@kernel.org> wrote:
> On Mon, Jul 27, 2020 at 02:38:52PM -0500, John Donnelly wrote:
> >
> >
> >>On Jul 27, 2020, at 2:18 PM, Sasha Levin <sashal@kernel.org> wrote:
> >>
> >>On Mon, Jul 27, 2020 at 11:00:14AM -0400, Mike Snitzer wrote:
> >>>This mail needs to be saent to stable@vger.kernel.org (now cc'd).
> >>>
> >>>Greg et al: please backport 2df3bae9a6543e90042291707b8db0cbfbae9ee9
> >>
> >>Hm, what's the issue that this patch addresses? It's not clear from the
> >>commit message.
> >>
> >>--
> >>Thanks,
> >>Sasha
> >
> >HI Sasha ,
> >
> >In an off-line conversation I had with Mike , he indicated that :
> >
> >
> >commit 1b17159e52bb31f982f82a6278acd7fab1d3f67b
> >Author: Mike Snitzer <snitzer@redhat.com>
> >Date: Fri Feb 28 18:00:53 2020 -0500
> >
> > dm bio record: save/restore bi_end_io and bi_integrity
> >
> >
> >commit 248aa2645aa7fc9175d1107c2593cc90d4af5a4e
> >Author: Mike Snitzer <snitzer@redhat.com>
> >Date: Fri Feb 28 18:11:53 2020 -0500
> >
> > dm integrity: use dm_bio_record and dm_bio_restore
> >
> >
> >Were picked up in "stable" kernels picked up even though
> >neither was marked for stable@vger.kernel.org
> >
> >Adding this missing commit :
> >
> >2df3bae9a6543e90042291707b8db0cbfbae9ee9
> >
> >
> >Completes the series
>
> Should we just revert those two commits instead if they're not needed?
I'd be fine with that, exceept I haven't looked to see whether any
other stable commits conflict with reverting them.
But you have my blessing to give it a shot ;)
Mike
next prev parent reply other threads:[~2020-07-27 20:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 13:40 (resend) [PATCH [linux-4.14.y]] dm cache: submit writethrough writes in parallel to origin and cache John Donnelly
2020-07-27 15:00 ` Mike Snitzer
2020-07-27 19:18 ` Sasha Levin
2020-07-27 19:38 ` John Donnelly
2020-07-27 20:17 ` Sasha Levin
2020-07-27 20:30 ` Mike Snitzer [this message]
2020-07-27 20:38 ` John Donnelly
2020-07-29 11:51 ` Greg KH
2020-07-29 11:55 ` Greg KH
2020-07-29 14:16 ` Mike Snitzer
2020-07-29 23:45 ` John Donnelly
2020-07-30 5:21 ` Greg KH
2020-07-30 14:40 ` John Donnelly
2020-07-31 6:36 ` Greg KH
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=20200727203025.GA28830@redhat.com \
--to=snitzer@redhat.com \
--cc=john.p.donnelly@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@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.