The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Edward Donovan <edward.donovan@numble.net>
Cc: "Wang, Warner" <warner.wang@hp.com>,
	"Wang, Song-Bo (Stoney)" <song-bo.wang@hp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: need help on a DEADLOCK problem related to function try_one_irq()
Date: Thu, 6 Dec 2012 13:23:40 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.02.1212061322060.2701@ionos> (raw)
In-Reply-To: <CADdbW+F0aO3Y1F+-Ywksmfy5J5xmRc+euwEO9B2frA=EfrRfGg@mail.gmail.com>

Ed,

On Thu, 6 Dec 2012, Edward Donovan wrote:
> So, let me try to confirm some things now, so I can learn as I go.  To
> spell out what's in the new patch:
> 
> The later line,
> 
>   action = desc->action;
> 
> should have been this all along?
> 
>   action = action->next;

Yes. My bad :(
 
> And with that fixed, the other test can go.  Which is good, now,
> because it was creating locking problems for you.
> 
> Ok, thanks for bearing with me.   I'll repeat the test here, some
> more, but they've generally behaved consistently and probably will
> keep showing the same.
> 
> I might as well add that I would happily ship one of these computers,
> with a reliably spurious interrupt, to Thomas in Germany. if that
> would help for testing.

I'm always happy to have machines which expose strange symptoms.

Thanks,

	tglx

      reply	other threads:[~2012-12-06 12:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DAE2ECFDBE54434BA3014E0CC0F2A1E87700075B@G4W3211.americas.hpqcorp.net>
     [not found] ` <alpine.LFD.2.02.1211221120580.2701@ionos>
     [not found]   ` <alpine.LFD.2.02.1211231008060.2701@ionos>
2012-11-26  8:09     ` need help on a DEADLOCK problem related to function try_one_irq() Wang, Warner
2012-11-27 20:31       ` Edward Donovan
2012-12-06  6:10       ` Edward Donovan
2012-12-06 12:23         ` 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.LFD.2.02.1212061322060.2701@ionos \
    --to=tglx@linutronix.de \
    --cc=edward.donovan@numble.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=song-bo.wang@hp.com \
    --cc=warner.wang@hp.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