public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Mickler <florian@mickler.org>
To: Borislav Petkov <bp@amd64.org>
Cc: Tobias Karnat <tobias.karnat@googlemail.com>,
	Borislav Petkov <bp@alien8.de>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: edac_core: crashes on shutdown
Date: Thu, 2 Dec 2010 19:14:12 +0100	[thread overview]
Message-ID: <20101202191412.288b82f8@schatten.dmk.lab> (raw)
In-Reply-To: <20101202170610.GE27263@aftab>

On Thu, 2 Dec 2010 18:06:10 +0100
Borislav Petkov <bp@amd64.org> wrote:

> From: Borislav Petkov <borislav.petkov@amd.com>
> Date: Thu, 2 Dec 2010 17:48:35 +0100
> Subject: [PATCH] EDAC: Fix workqueue-related crashes
> 
> 00740c58541b6087d78418cebca1fcb86dc6077d changed edac_core to
> un-/register a workqueue item only if a lowlevel driver supplies a
> polling routine. Normally, when we remove a polling low-level driver,
> we go and teardown the workqueue and cancel all the queued work.
> However, the workqueue unreg happens based on the ->op_state setting,
> and edac_mc_del_mc() sets this to OP_OFFLINE _before_ we cancel the work
> item, leading to NULL ptr oops on the workqueue list.
> 
> Fix it by putting the unreg stuff in proper order.

Yes. That should work. Once we stopped the workqueue and removed it
from the global list, do we actually need to set it to OP_OFFLINE?

Also 00740c585 did fix a hang in edac_mc.c... could this also
happen in the edac_device_del_device/edac_pci_del_device functions? 

Regards,
Flo


  parent reply	other threads:[~2010-12-02 18:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 11:01 edac_core: crashes on shutdown Tobias Karnat
2010-12-01 12:39 ` Borislav Petkov
2010-12-01 13:24   ` Tobias Karnat
2010-12-01 14:33     ` Borislav Petkov
2010-12-01 17:46       ` Tobias Karnat
2010-12-01 19:35         ` Borislav Petkov
2010-12-02  9:03           ` Tobias Karnat
2010-12-02 14:51             ` Florian Mickler
2010-12-02 14:52               ` Florian Mickler
2010-12-02 15:21             ` Borislav Petkov
2010-12-02 16:21               ` Tobias Karnat
2010-12-02 17:02                 ` Florian Mickler
2010-12-02 17:07                   ` Borislav Petkov
2010-12-02 17:06                 ` Borislav Petkov
2010-12-02 18:05                   ` Tobias Karnat
2010-12-02 18:37                     ` Borislav Petkov
2010-12-02 22:34                       ` Tobias Karnat
2010-12-03 11:58                         ` Borislav Petkov
2010-12-03 21:23                       ` Doug Thompson
2010-12-02 18:14                   ` Florian Mickler [this message]
2010-12-02 18:51                     ` Borislav Petkov
2010-12-02 19:54                       ` Florian Mickler

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=20101202191412.288b82f8@schatten.dmk.lab \
    --to=florian@mickler.org \
    --cc=bp@alien8.de \
    --cc=bp@amd64.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tobias.karnat@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox