From: Mel Gorman <mgorman@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Tejun Heo <tj@kernel.org>, Xiaotian Feng <dannyfeng@tencent.com>,
Neela Syam Kolli <megaraidlinux@lsi.com>,
"James E.J. Bottomley" <JBottomley@parallels.com>,
linux-scsi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 3.7-rc8 boot failure due to recent workqueue-related patch
Date: Sun, 9 Dec 2012 11:11:46 +0000 [thread overview]
Message-ID: <20121209111146.GB1009@suse.de> (raw)
In-Reply-To: <alpine.LFD.2.02.1212081647500.4593@air.linux-foundation.org>
On Sat, Dec 08, 2012 at 04:50:21PM -0800, Linus Torvalds wrote:
>
>
> On Sat, 8 Dec 2012, Mel Gorman wrote:
> >
> > Commit 8852aac2 (workqueue: mod_delayed_work_on() shouldn't queue timer on
> > 0 delay) is causing the following boot failure for me. Found by bisection
> > but no further analysis unfortunately until I get back home properly.
> > I've added the relevant maintainers for megasas and SCSI in case it's
> > somehow specific to that driver.
>
> This should be fixed by commit c1d390d8e612. The Megaraid SAS driver was
> doing insane things, using a work-struct for delayed work, and casting
> pointers around. It had happened to work for all the wrong reasons before,
> the mod_delayed_work_on() changes just exposed how crazy that crap was.
>
Correct, it is fixed by commit c1d390d8e612. Sorry for the noise.
--
Mel Gorman
SUSE Labs
prev parent reply other threads:[~2012-12-09 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 20:35 3.7-rc8 boot failure due to recent workqueue-related patch Mel Gorman
2012-12-09 0:50 ` Linus Torvalds
2012-12-09 11:11 ` Mel Gorman [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=20121209111146.GB1009@suse.de \
--to=mgorman@suse.de \
--cc=JBottomley@parallels.com \
--cc=dannyfeng@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=megaraidlinux@lsi.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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 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.