From: Borislav Petkov <bp@alien8.de>
To: Sasha Levin <sashal@kernel.org>,
Victoria Anosova <v.s.anosova@gmail.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
x86@kernel.org, Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] x86/fpu: Disable BH while while loading FPU registers in __fpu__restore_sig()
Date: Tue, 20 Nov 2018 19:34:43 +0100 [thread overview]
Message-ID: <20181120183443.GJ2527@zn.tnic> (raw)
In-Reply-To: <20181120132531.6E80C206BB@mail.kernel.org>
On Tue, Nov 20, 2018 at 01:25:30PM +0000, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
>
> The bot has tested the following trees: v4.19.2, v4.18.19, v4.14.81, v4.9.137, v4.4.163, v3.18.125.
>
> v4.19.2: Build OK!
> v4.18.19: Build OK!
> v4.14.81: Build OK!
> v4.9.137: Failed to apply! Possible dependencies:
> Unable to calculate
AFAIR, Victoria asked about this fix a while ago. CCed.
Victoria, do you still need this patch in your 4.9? If so, you might
wanna give it a try:
https://git.kernel.org/tip/68239654acafe6aad5a3c1dc7237e60accfebc03
Let us know if you need help backporting - it should be easy though.
HTH.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next parent reply other threads:[~2018-11-20 18:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181119160410.ne7oiq2gkwt6jiqg@linutronix.de>
[not found] ` <20181120132531.6E80C206BB@mail.kernel.org>
2018-11-20 18:34 ` Borislav Petkov [this message]
2018-11-21 6:11 ` [PATCH v2] x86/fpu: Disable BH while while loading FPU registers in __fpu__restore_sig() Victoria Anosova
2018-11-21 10:56 ` Borislav Petkov
2018-11-21 12:41 ` Victoria Anosova
2018-11-21 12:54 ` Boris Petkov
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=20181120183443.GJ2527@zn.tnic \
--to=bp@alien8.de \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=v.s.anosova@gmail.com \
--cc=x86@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