public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Clayton <chris2553@googlemail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
	James Bottomley <James.Bottomley@hansenpartnership.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, 8 Jun 2009 21:03:53 +0100	[thread overview]
Message-ID: <200906082103.53281.chris2553@googlemail.com> (raw)
In-Reply-To: <c6b1100b0906081217t57484774w475f79a93d37c221@mail.gmail.com>

On Monday 08 June 2009, Chris Clayton wrote:
> Linus,
>
> 2009/6/8 Linus Torvalds <torvalds@linux-foundation.org>:
> > On Mon, 8 Jun 2009, Chris Clayton wrote:
> >> I can confirm that a kernel built with Jaswinder's patch applied
> >> survived 200 boots without a panic.
> >
> > Ok, goodie.
> >
> > Can you confirm that the further cleanup (removing the pointless 'ret'
> > variable and the useless empty checking around 'for_each_entry') also
> > works for you?
> >
> >                Linus
> >
> > ---
> >  kernel/async.c |   15 +++++----------
> >  1 files changed, 5 insertions(+), 10 deletions(-)
> >
> > diff --git a/kernel/async.c b/kernel/async.c
> > index 5054030..27235f5 100644
> > --- a/kernel/async.c
> > +++ b/kernel/async.c
> > @@ -92,23 +92,18 @@ extern int initcall_debug;
> >  static async_cookie_t  __lowest_in_progress(struct list_head *running)
> >  {
> >        struct async_entry *entry;
> > -       async_cookie_t ret = next_cookie; /* begin with "infinity" value
> > */
> >
> >        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;
> > -                       }
> > -       }
> > +       list_for_each_entry(entry, &async_pending, list)
> > +               if (entry->running == running)
> > +                       return entry->cookie;
> >
> > -       return ret;
> > +       return next_cookie;     /* "infinity" value */
> >  }
> >
> >  static async_cookie_t  lowest_in_progress(struct list_head *running)
>
> Yes, rc8-git5 with your patch applied has booted 100 times without a panic.
>

...so I should have added:

Tested-by: Chris Clayton <chris2553@googlemail.com>

> May I add that the people who thought of, designed and implemented
> kexec should have a large and shiny medals pinned to their chests.
> Well over 1000 kernel boots have been executed on my PC today and, if
> I hadn't been able to do that automatically with a few lines of script
> at the head of /etc/rc.d/rc.local, I would have been bleary-eyed
> before noon :-)
>
> Chris



-- 
No, Sir; there is nothing which has yet been contrived by man, by which
so much happiness is produced as by a good tavern or inn - Doctor Samuel
Johnson
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-06-08 20:04 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
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 [this message]
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=200906082103.53281.chris2553@googlemail.com \
    --to=chris2553@googlemail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=arjan@linux.intel.com \
    --cc=jaswinder@kernel.org \
    --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