All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@o2.pl>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Jiri Slaby <jirislaby@gmail.com>,
	"Rafael J\. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@ucw.cz>,
	linux-pm@lists.linux-foundation.org,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.21-mm1 hwsusp: BUG at workqueue.c:106
Date: Tue, 8 May 2007 14:12:33 +0200	[thread overview]
Message-ID: <20070508121232.GE1772@ff.dom.local> (raw)
In-Reply-To: <20070508105528.GA86@tv-sign.ru>

On 08-05-2007 12:55, Oleg Nesterov wrote:
> On 05/08, Andrew Morton wrote:
>> On Tue, 08 May 2007 10:57:35 +0200 Jiri Slaby <jirislaby@gmail.com> wrote:
>>
>>> this occured in dmesg during resuming from hwsusp in 2.6.21-mm1 (captured
>>> through netconsole). Perfectly reproducible, it simply happens each time I
>>> try it.
>> Let's cc Oleg.
>>
>>> usb_endpoint usbdev5.1_ep00: PM: resume from 0, parent usb5 still 2
>>> ------------[ cut here ]------------
>>> kernel BUG at /home/l/latest/xxx/kernel/workqueue.c:106!
>>> invalid opcode: 0000 [#1]
>>> SMP
>>> Modules linked in: ipv6 floppy ohci1394 ieee1394 parport_pc parport usbhid
>>> ehci_hcd pata_acpi ff_memless sr_mod cdrom
...
> queue_delayed_work().
> 
> Probably, cancel_delayed_work(&delayed_work->work) was called with the ->timer
> pending. This is wrong, cancel_delayed_work() clears _PENDING unconditionally,

Maybe I miss your point, but clearing is conditional: on timer delete...

I think more suspicious is calling cancel_work_sync() for a delayed work
(with timer pending). Or maybe some race profits from _PENDING cleared
without locking?

BTW, it seems some debugging is needed to show, whose work is doing the
mess.

Regards,
Jarek P.

  parent reply	other threads:[~2007-05-08 12:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08  8:57 2.6.21-mm1 hwsusp: BUG at workqueue.c:106 Jiri Slaby
2007-05-08  9:11 ` Andrew Morton
2007-05-08 10:55   ` Oleg Nesterov
2007-05-08 10:55   ` Oleg Nesterov
2007-05-08 11:09     ` Jiri Slaby
2007-05-08 12:00       ` Jiri Slaby
2007-05-08 12:00       ` Jiri Slaby
2007-05-08 13:48         ` Oleg Nesterov
2007-05-08 14:20           ` Oleg Nesterov
2007-05-08 14:20           ` Oleg Nesterov
2007-05-08 14:30             ` [PATCH 1/1] vmstat-use-our-own-timer-events-fix Jiri Slaby
2007-05-08 14:42               ` Oleg Nesterov
2007-05-08 14:42               ` Oleg Nesterov
2007-05-08 16:08               ` Christoph Lameter
2007-05-08 16:08               ` Christoph Lameter
2007-05-08 14:30             ` Jiri Slaby
2007-05-08 13:48         ` 2.6.21-mm1 hwsusp: BUG at workqueue.c:106 Oleg Nesterov
2007-05-08 11:09     ` Jiri Slaby
2007-05-08 12:12     ` Jarek Poplawski [this message]
2007-05-08 12:40       ` Oleg Nesterov
2007-05-08 12:40       ` Oleg Nesterov
2007-05-08 12:12     ` Jarek Poplawski
2007-05-08  9:11 ` Andrew Morton
2007-05-08 10:51 ` Jarek Poplawski
2007-05-08 10:51 ` Jarek Poplawski
  -- strict thread matches above, loose matches on Subject: below --
2007-05-08  8:57 Jiri Slaby

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=20070508121232.GE1772@ff.dom.local \
    --to=jarkao2@o2.pl \
    --cc=akpm@linux-foundation.org \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=oleg@tv-sign.ru \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    /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.