All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: ???? ?? <mauriceliu27@hotmail.com>
Cc: linux-kernel@vger.kernel.org,
	nick piggin <nickpiggin@yahoo.com.au>,
	drzeus@drzeus.cx
Subject: Re: [BUG] AS-ioscheduler: kernel panic at as_exit_queue
Date: Fri, 9 Jan 2009 09:05:17 +0100	[thread overview]
Message-ID: <20090109080517.GI32491@kernel.dk> (raw)
In-Reply-To: <COL120-W718F2E0FBF40D8870415BFDEDC0@phx.gbl>

On Thu, Jan 08 2009, ???? ?? wrote:
> 
> Hi Nick & Jens,
> 
>  I met a Kernel Panic with AS, the panic pc is at as_exit_queue, and panic
>  when the function check whether the fifo_list[REQ_SYNC] and
>  fifo_list[REQ_ASYNC] are empty or not, it would Panic if the lists are not
> empty.
> 
>       The k-panic happened when I plugged out my Micro-SD memory card
>  from my phone, the log has been attached onto this mail.
> 
>       I guess there may be some conflicts between AS and Hot-plug
>  mechanism, so I read the code of AS code by code to find anything
>  suspicious. I find that AS might does not consider that do any operations
>  to the fifo_lists when the device driver try to exit its elevator, so there
>  is possibility that when device try to exit, the fifo_lists are not empty,
>  and happen kernel panic, though the possibility is really really very
>  small:).
> 
>       Unfortunately, I have met such k-panic more than two times, so I
>  think I should get your suggestions first, and then try to do some works
>  for this problem:) Look forward for your reply:)
> 
> My Linux version :  2.6.25

Please try a newer version, I _think_ this was fixed in sd. CC'ing
Pierre, just in case.

-- 
Jens Axboe


       reply	other threads:[~2009-01-09  8:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <COL120-W718F2E0FBF40D8870415BFDEDC0@phx.gbl>
2009-01-09  8:05 ` Jens Axboe [this message]
2009-01-12 15:18   ` [BUG] AS-ioscheduler: kernel panic at as_exit_queue Pierre Ossman

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=20090109080517.GI32491@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=drzeus@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mauriceliu27@hotmail.com \
    --cc=nickpiggin@yahoo.com.au \
    /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.