All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Ed Lin <ed.lin@promise.com>
Cc: "jens.axboe" <jens.axboe@oracle.com>,
	akpm <akpm@linux-foundation.org>, jeff <jeff@garzik.org>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: stex driver panic in kernel 2.6.23
Date: Wed, 24 Oct 2007 15:17:56 -0400	[thread overview]
Message-ID: <1193253476.3441.7.camel@localhost.localdomain> (raw)
In-Reply-To: <1193253355.3441.4.camel@localhost.localdomain>

On Wed, 2007-10-24 at 15:16 -0400, James Bottomley wrote:
> On Wed, 2007-10-24 at 11:59 -0700, Ed Lin wrote:
> > The shared tag issue was not fixed yet. Kernel panic
> > happened while running I/O test in kernel 2.6.23
> > (information attached). After applying the patch I posted
> > (or the version James modified), panic disappeared.
> > Switch back to standard kernel, panic again.
> 
> Just so we're on the same page, do you have a pointer to the patch?
> 
> I thought the issue was fixed by this patch
> 
> http://marc.info/?l=linux-scsi&m=118968649513338
> 
> Which Linus said he modified and then committed here:
> 
> http://marc.info/?l=linux-kernel&m=118969824104600
> 
> However, I have to confess I can't find this patch in the current
> kernel.

Found it; it's commit f3da54ba140c6427fa4a32913e1bf406f41b5dda. So we
still have some problem, even with this patch.

James



  reply	other threads:[~2007-10-24 19:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 18:59 stex driver panic in kernel 2.6.23 Ed Lin
2007-10-24 19:15 ` James Bottomley
2007-10-24 19:17   ` James Bottomley [this message]
2007-10-24 19:17 ` Andrew Morton
2007-10-24 19:29   ` James Bottomley
2007-10-25  8:11     ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2007-10-29 17:46 Ed Lin
2007-10-29 20:22 ` Jens Axboe

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=1193253476.3441.7.camel@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=akpm@linux-foundation.org \
    --cc=ed.lin@promise.com \
    --cc=jeff@garzik.org \
    --cc=jens.axboe@oracle.com \
    --cc=linux-scsi@vger.kernel.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 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.