public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Chris Clayton <chris2553@googlemail.com>,
	NeilBrown <neilb@suse.de>,
	linux-kernel@vger.kernel.org, scsi <linux-scsi@vger.kernel.org>,
	Tejun Heo <tj@kernel.org>,
	Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: 2.6.30-rc8 Oops whilst booting
Date: Mon, 08 Jun 2009 22:36:30 +0530	[thread overview]
Message-ID: <1244480790.2716.7.camel@ht.satnam> (raw)
In-Reply-To: <1244479879.4079.284.camel@mulgrave.site>

On Mon, 2009-06-08 at 16:51 +0000, James Bottomley wrote:
> On Mon, 2009-06-08 at 09:21 -0700, Linus Torvalds wrote:
> > 
> > On Mon, 8 Jun 2009, Chris Clayton wrote:
> > > 
> > > OK. I reversed that change and built and installed the kernel. It has
> > > withstood 100 reboots without a panic. Additionally, I pulled the
> > > latest changes (that will be rc8-git5, I think) from kernel.org,
> > > reversed the change to that kernel and built and installed it. That
> > > too withstood 100 reboots without a panic.
> > > 
> > > Let me know if there's anything else I can do to help fix this.
> > 
> > That's already pretty convincing.
> > 
> > James, Arjan? The original oops message is here (a jpg screen capture, 
> > unable to open initial console):
> > 
> > 	http://lkml.org/lkml/2009/6/6/142
> > 
> > and it's this bug entry:
> > 
> > 	Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13474
> > 	Subject         : Oops whilst booting
> > 	Submitter       : Chris Clayton <chris2553@googlemail.com>
> > 	Date            : 2009-06-06 18:59 (2 days old)
> > 	References      : http://marc.info/?l=linux-kernel&m=124431487924254&w=4
> > 
> > and now bisected down to 
> > 
> > >> commit d5a877e8dd409d8c702986d06485c374b705d340
> > >> Author: James Bottomley <James.Bottomley@HansenPartnership.com>
> > >> Date:   Sun May 24 13:03:43 2009 -0700
> > >>
> > >>     async: make sure independent async domains can't accidentally entangle
> > 
> > please advice. Otherwise I'll have to revert.
> 
> The root cause is a reordering of the devices caused by the async code.
> 
> I suspect it's a bug in async that was obscured by the old behaviour of
> async_synchronize.. (or it's a bug in the new code) ... how long do I
> have to find out which?
> 

But reverting your patch Or if we return like this also fix chris
problem :

diff --git a/kernel/async.c b/kernel/async.c
index 94dd36f..3b492cb 100644
--- a/kernel/async.c
+++ b/kernel/async.c
@@ -96,15 +96,13 @@ static async_cookie_t  __lowest_in_progress(struct list_head *running)
 	if (!list_empty(running)) {
 		entry = list_first_entry(running,
 			struct async_entry, list);
-		ret = entry->cookie;
+		return entry->cookie;
 	}
 
 	if (!list_empty(&async_pending)) {
 		list_for_each_entry(entry, &async_pending, list)
-			if (entry->running == running) {
-				ret = entry->cookie;
-				break;
-			}
+			if (entry->running == running)
+				return entry->cookie;
 	}
 
 	return ret;



  reply	other threads:[~2009-06-08 17:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200906061959.55592.chris2553@googlemail.com>
     [not found] ` <200906062215.30571.chris2553@googlemail.com>
     [not found]   ` <1244381140.30664.12.camel@ht.satnam>
     [not found]     ` <c6b1100b0906071138g2c46fb34vc1a2beb9438f1f1e@mail.gmail.com>
2009-06-07 22:31       ` 2.6.30-rc8 Oops whilst booting Jaswinder Singh Rajput
2009-06-07 22:55         ` NeilBrown
2009-06-08  8:08           ` Chris Clayton
2009-06-08 10:58             ` Chris Clayton
2009-06-08 11:34               ` Jaswinder Singh Rajput
2009-06-08 12:53                 ` Chris Clayton
2009-06-08 16:21                   ` Linus Torvalds
2009-06-08 16:51                     ` James Bottomley
2009-06-08 17:06                       ` Jaswinder Singh Rajput [this message]
2009-06-08 17:45                         ` Chris Clayton
2009-06-08 18:21                           ` Linus Torvalds
2009-06-08 19:17                             ` Chris Clayton
2009-06-08 20:03                               ` Chris Clayton
2009-06-08 17:21                       ` Linus Torvalds
2009-06-08 17:37                         ` Arjan van de Ven
2009-06-08 17:38                         ` James Bottomley
2009-06-08 17:06                     ` James Bottomley
2009-06-08 17:42                       ` Linus Torvalds
2009-06-08 17:49                         ` James Bottomley
2009-06-08 18:33                       ` Chris Clayton
2009-06-08 14:23             ` James Bottomley
2009-06-08 15:04               ` Chris Clayton
2009-06-08 15:17               ` Chris Clayton
2009-06-08 15:32                 ` James Bottomley

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=1244480790.2716.7.camel@ht.satnam \
    --to=jaswinder@kernel.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=arjan@linux.intel.com \
    --cc=chris2553@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=neilb@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox