From: Luis Henriques <lhenriques@suse.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>, Jeff Layton <jlayton@kernel.org>,
Ilya Dryomov <idryomov@gmail.com>,
ceph-devel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 0/2] stable CephFS backports
Date: Fri, 10 Apr 2020 11:20:59 +0100 [thread overview]
Message-ID: <20200410102059.GA18283@suse.com> (raw)
In-Reply-To: <20200410091410.GF1691838@kroah.com>
On Fri, Apr 10, 2020 at 11:14:10AM +0200, Greg Kroah-Hartman wrote:
> On Wed, Apr 08, 2020 at 11:58:38AM +0100, Luis Henriques wrote:
> > Hi!
> >
> > Please pick the backports for the following upstream commits:
> >
> > 4fbc0c711b24 "ceph: remove the extra slashes in the server path"
> > b27a939e8376 "ceph: canonicalize server path in place"
> >
> > They fix an ancient bug that can be reproduced in kernels as old as 4.9 (I
> > couldn't reproduced it with 4.4).
>
> All now queued up, including for 5.5.y, thanks.
Awesome, thanks. And sorry, I forgot to mention in the cover-letter that
5.5 was a clean cherry-pick.
Cheers,
--
Luís
prev parent reply other threads:[~2020-04-10 10:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 10:58 [PATCH 0/2] stable CephFS backports Luis Henriques
2020-04-08 10:58 ` [PATCH 4.9 1/2] ceph: remove the extra slashes in the server path Luis Henriques
2020-04-08 10:58 ` [PATCH 4.9 2/2] ceph: canonicalize server path in place Luis Henriques
2020-04-08 10:58 ` [PATCH 4.14,4.19 1/2] ceph: remove the extra slashes in the server path Luis Henriques
2020-04-08 10:58 ` [PATCH 4.14,4.19 2/2] ceph: canonicalize server path in place Luis Henriques
2020-04-08 10:58 ` [PATCH 5.4 1/2] ceph: remove the extra slashes in the server path Luis Henriques
2020-04-10 9:11 ` Greg Kroah-Hartman
2020-04-08 10:58 ` [PATCH 5.4 2/2] ceph: canonicalize server path in place Luis Henriques
2020-04-08 13:45 ` [PATCH 0/2] stable CephFS backports Luis Henriques
2020-04-08 14:50 ` Luis Henriques
2020-04-10 9:14 ` Greg Kroah-Hartman
2020-04-10 10:20 ` Luis Henriques [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=20200410102059.GA18283@suse.com \
--to=lhenriques@suse.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=idryomov@gmail.com \
--cc=jlayton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).