All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	thomas.lendacky@amd.com
Subject: Re: [5.0.0 rc3 BUG] possible irq lock inversion dependency detected
Date: Thu, 18 Apr 2019 21:52:36 +0500	[thread overview]
Message-ID: <CABXGCsP414BbijQQ+NJkCV83zdCKcfCyR0NBwyor6z3T8CawDg@mail.gmail.com> (raw)
In-Reply-To: <CABXGCsNaw=mb0YF4Bkd5_CTwMfU=dNZ=RTV96dwO=UQy=n_gOQ@mail.gmail.com>

On Mon, 15 Apr 2019 at 01:07, Mikhail Gavrilov
<mikhail.v.gavrilov@gmail.com> wrote:
>
>
> Thanks, with this patch problem was gone.
> We have time land it in 5.1?
>

I received automated email with follow content:

> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: 1f50ddb4f418 x86/speculation: Handle HT correctly on AMD.
>
> The bot has tested the following trees: v5.0.7, v4.19.34, v4.14.111, v4.9.168, v4.4.178.
>
> v5.0.7: Build OK!
> v4.19.34: Build OK!
> v4.14.111: Build failed! Errors:
>     arch/x86/kernel/process.c:417:2: error: implicit declaration of function ‘lockdep_assert_irqs_disabled’; did you mean ‘lockdep_assert_cpus_held’? [-Werror=implicit-function-declaration]
>
> v4.9.168: Failed to apply! Possible dependencies:
>     01daf56875ee ("x86/speculation: Reorganize speculation control MSRs update")
>     26c4d75b2340 ("x86/speculation: Rename SSBD update functions")
>     5bfbe3ad5840 ("x86/speculation: Prepare for per task indirect branch speculation control")
>
> v4.4.178: Failed to apply! Possible dependencies:
>     01daf56875ee ("x86/speculation: Reorganize speculation control MSRs update")
>     26c4d75b2340 ("x86/speculation: Rename SSBD update functions")
>     5bfbe3ad5840 ("x86/speculation: Prepare for per task indirect branch speculation control")
>     cc69b3498921 ("x86/bugs: Unify x86_spec_ctrl_{set_guest,restore_host}")
>
>
> How should we proceed with this patch?

So I wonder is any further actions are required for merging patch to mainline?

--
Best Regards,
Mike Gavrilov.

  reply	other threads:[~2019-04-18 16:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-02 18:33 [5.0.0 rc3 BUG] possible irq lock inversion dependency detected Mikhail Gavrilov
2019-04-14 17:33 ` Mikhail Gavrilov
2019-04-14 17:51   ` Thomas Gleixner
2019-04-14 20:07     ` Mikhail Gavrilov
2019-04-18 16:52       ` Mikhail Gavrilov [this message]
2019-04-18 19:17         ` Thomas Gleixner
2019-04-14 21:10     ` [tip:x86/urgent] x86/speculation: Prevent deadlock on ssb_state::lock tip-bot for Thomas Gleixner
     [not found]       ` <20190415130916.BAC1020684@mail.kernel.org>
2019-04-15 16:13         ` Thomas Gleixner

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=CABXGCsP414BbijQQ+NJkCV83zdCKcfCyR0NBwyor6z3T8CawDg@mail.gmail.com \
    --to=mikhail.v.gavrilov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    /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.