mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Tejun Heo <tj@kernel.org>
Cc: nick <xerofoify@gmail.com>,
	jiangshanlai@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: Workqueue change with commit id,1bd04bf6f breaks mpt3sas scsi driver
Date: Fri, 25 Mar 2016 09:32:05 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.11.1603250925350.3978@nanos> (raw)
In-Reply-To: <20160324193914.GC7822@mtj.duckdns.org>

On Thu, 24 Mar 2016, Tejun Heo wrote:
> On Wed, Mar 23, 2016 at 10:28:16PM -0400, nick wrote:
> > Seems that commit id, 1bd04bf6f breaks the mpt3sas driver according to this bug report:
> > https://bugzilla.kernel.org/show_bug.cgi?id=114611. Seems that the driver is fine as
> > have inspection all the driver functions are wrappers around  queue_delayed_work and
> > according to the person's debugging this commit breaks it. However they are not sure
> > if it's the driver or the timer subsystem. I am assuming it's the timer subsystem as 
> > the driver is just using wrapper functions around core workqueue functions with irqs
> > disabled and a spin lock held.
> 
> Hmmm... 1bd04bf6f68d ("timer: Remove FIFO "guarantee"") doesn't look
> like an easy change to undo and it sounds like the driver was already
> (subtly) broken even before the commit given that ordered workqueues
> are not affine to any CPU and timer expirations across different CPUs
> aren't strictly ordered.  Unfortunately, the only way forward seems to
> be implementing ordering from the driver's side.

The changelog explains in detail, that the FIFO "guarantee" did not exist for
a long time. Certainly that commit removed the last reminders of that so
called guarantee, but anything relying on FIFO ordering of the timer wheel was
broken before that commit. Just because it "worked" before that commit does
not mean it was correct.

Thanks,

	tglx

      reply	other threads:[~2016-03-25  8:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <56F350C0.5070000@gmail.com>
2016-03-24 19:39 ` Tejun Heo
2016-03-25  8:32   ` Thomas Gleixner [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=alpine.DEB.2.11.1603250925350.3978@nanos \
    --to=tglx@linutronix.de \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    --cc=xerofoify@gmail.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

all inboxes | Powered by JetHome®