From: Johannes Thumshirn <jthumshirn@suse.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: dsterba@suse.com, nborisov@suse.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] btrfs: correctly validate compression type" failed to apply to 5.1-stable tree
Date: Tue, 23 Jul 2019 14:30:22 +0200 [thread overview]
Message-ID: <20190723123018.GF3997@x250.microfocus.com> (raw)
In-Reply-To: <20190723122817.GB11835@kroah.com>
On Tue, Jul 23, 2019 at 02:28:17PM +0200, Greg KH wrote:
> On Tue, Jul 23, 2019 at 02:19:55PM +0200, Johannes Thumshirn wrote:
> > Hi Greg,
> >
> > please try the following:
> >
> > >From 9afa2d46ecb511259130eb51b4ab1feb1055d961 Mon Sep 17 00:00:00 2001
> > From: Johannes Thumshirn <jthumshirn@suse.de>
> > Date: Thu, 6 Jun 2019 12:07:15 +0200
> > Subject: [PATCH] btrfs: correctly validate compression type
> >
> > (commit aa53e3bfac7205fb3a8815ac1c937fd6ed01b41e upstream)
>
> Worked for 5.1.y and 4.19.y, but not for the older ones.
But 4.19 lacks the buggy commit, doesn't it?
--
Johannes Thumshirn SUSE Labs Filesystems
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2019-07-23 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 12:01 FAILED: patch "[PATCH] btrfs: correctly validate compression type" failed to apply to 5.1-stable tree gregkh
2019-07-23 12:19 ` Johannes Thumshirn
2019-07-23 12:28 ` Greg KH
2019-07-23 12:30 ` Johannes Thumshirn [this message]
2019-07-23 12:40 ` Greg KH
2019-07-23 12:43 ` Johannes Thumshirn
2019-07-23 22:31 ` Thomas Backlund
2019-07-24 6:29 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2019-07-24 5:45 gregkh
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=20190723123018.GF3997@x250.microfocus.com \
--to=jthumshirn@suse.de \
--cc=dsterba@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=nborisov@suse.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 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.