public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Jose Ricardo Ziviani <joserz@linux•vnet.ibm.com>,
	linuxppc-dev@lists•ozlabs.org
Cc: benh@au1•ibm.com, david@gibson•dropbear.id.au
Subject: Re: [v3, 1/1] powerpc/pseries: Make RAS IRQ explicitly dependent on DLPAR WQ
Date: Thu, 11 Jan 2018 13:25:43 +1100 (AEDT)	[thread overview]
Message-ID: <3zH8qq1SWkz9sRW@ozlabs.org> (raw)
In-Reply-To: <20180103211252.24615-2-joserz@linux.vnet.ibm.com>

On Wed, 2018-01-03 at 21:12:52 UTC, Jose Ricardo Ziviani wrote:
> The hotplug engine uses its own workqueue to handle IRQ requests, the
> problem is that such workqueue is initialized after init_ras_IRQ, which
> will cause a kernel panic if any hotplug interruption is issued in that
> period of time.
> 
> This patch makes RAS IRQ registration explicitly dependent on DLPAR
> workqueue and adds a check to make sure that the workqueue is not
> initialized more than once.
> 
> Reported-by: Min Deng <mdeng@redhat•com>
> Reported-by: Daniel Henrique Barboza <danielhb@linux•vnet.ibm.com>
> Tested-by: Jose Ricardo Ziviani <joserz@linux•vnet.ibm.com>
> Signed-off-by: Michael Ellerman <mpe@ellerman•id.au>
> Reviewed-by: David Gibson <david@gibson•dropbear.id.au>

Applied to powerpc fixes, thanks.

https://git.kernel.org/powerpc/c/e2d5915293ffdff977ddcfc12b817b

cheers

      parent reply	other threads:[~2018-01-11  2:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 21:12 [PATCH v3 0/1] Make RAS IRQ explicitly dependent on DLPAR workqueue Jose Ricardo Ziviani
2018-01-03 21:12 ` [PATCH v3 1/1] powerpc/pseries: Make RAS IRQ explicitly dependent on DLPAR WQ Jose Ricardo Ziviani
2018-01-04  0:48   ` David Gibson
2018-01-11  2:25   ` Michael Ellerman [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=3zH8qq1SWkz9sRW@ozlabs.org \
    --to=patch-notifications@ellerman$(echo .)id.au \
    --cc=benh@au1$(echo .)ibm.com \
    --cc=david@gibson$(echo .)dropbear.id.au \
    --cc=joserz@linux$(echo .)vnet.ibm.com \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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