From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>
Subject: Re: Patches to apply to stable releases [6/17/2020]
Date: Fri, 26 Jun 2020 15:40:15 -0700 [thread overview]
Message-ID: <20200626224015.GA256865@roeck-us.net> (raw)
In-Reply-To: <20200626140413.GA4098272@kroah.com>
On Fri, Jun 26, 2020 at 04:04:13PM +0200, Greg Kroah-Hartman wrote:
> On Wed, Jun 17, 2020 at 04:53:08PM -0700, Guenter Roeck wrote:
> > Upstream commit 64611a15ca9d ("dm crypt: avoid truncating the logical block size")
> > upstream: v5.8-rc1
> > Fixes: ad6bf88a6c19 ("block: fix an integer overflow in logical block size")
> > in linux-4.4.y: b8cd70b724f0
> > in linux-4.9.y: 5dbde467ccd6
> > in linux-4.14.y: 0c7a7d8e62bd
> > in linux-4.19.y: a7f79052d1af
> > in linux-5.4.y: 6eed26e35cfd
> > upstream: v5.5-rc7
> > Affected branches:
> > linux-4.4.y (conflicts - backport needed)
> > linux-4.9.y (conflicts - backport needed)
> > linux-4.14.y
> > linux-4.19.y
> > linux-5.4.y
> > linux-5.6.y
> > linux-5.7.y
>
> Can you provide a backport for this?
>
That one is easy: 4.9.y and 4.4.y are not affected even though ad6bf88a6c19
has been applied there. Reason is that 64611a15ca9d only applies if
bc9e9cf0401f1 ("dm crypt: don't decrease device limits") is in the tree.
This in turn is a fix for 8f0009a22517 ("dm crypt: optionally support
larger encryption sector size"). None of those is in v4.4.y/v4.9.y.
> > Upstream commit 2f02fd3fa13e ("fanotify: fix ignore mask logic for events on child and on dir")
> > upstream: v5.8-rc1
> > Fixes: b469e7e47c8a ("fanotify: fix handling of events on child sub-directory")
> > in linux-4.9.y: 987d8ff3a2d8
> > in linux-4.14.y: 515160e3c4f2
> > in linux-4.19.y: 20663629f6ae
> > upstream: v4.20-rc3
> > Affected branches:
> > linux-4.9.y (conflicts - backport needed)
> > linux-4.14.y (conflicts - backport needed)
> > linux-4.19.y
> > linux-5.4.y (already applied)
> > linux-5.6.y (already applied)
> > linux-5.7.y (already applied)
>
> Do you have a backport?
>
I _think_ this doesn't apply either because it also depends on
837a393438475 ("fanotify: generalize fanotify_should_send_event()")
which is not in v4.14.y and earlier, but I may be wrong. That code
isn't exactly easy to understand.
> For all other patches you listed, I've queued up the missing ones, some
> already got merged since you sent this out.
>
Thanks!
Guenter
prev parent reply other threads:[~2020-06-26 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 23:53 Patches to apply to stable releases [6/17/2020] Guenter Roeck
2020-06-26 14:04 ` Greg Kroah-Hartman
2020-06-26 22:40 ` Guenter Roeck [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=20200626224015.GA256865@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.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.