From: James Bottomley <James.Bottomley@SteelEye.com>
To: Andreas Herrmann <aherrman@de.ibm.com>
Cc: Jens Axboe <axboe@suse.de>, James Bottomley <jejb@SteelEye.com>,
Linux SCSI <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] limit recursion when flushing shost->starved_list
Date: Sat, 19 Aug 2006 13:30:29 -0700 [thread overview]
Message-ID: <1156019429.3726.18.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20060809153116.GA14043@lion28.ibm.com>
On Wed, 2006-08-09 at 17:31 +0200, Andreas Herrmann wrote:
> Attached is a patch that should limit a possible recursion that can
> lead to a stack overflow like follows:
Well, OK, initially I'll put this in scsi-misc, since I acknowledge its
a problem. However, it is one that block queue grouping should be able
to get us out of ... and at that time, this code (and most of the
starved list handling) should exit the scsi mid-layer.
James
next prev parent reply other threads:[~2006-08-19 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 15:31 Andreas Herrmann
2006-08-19 20:30 ` James Bottomley [this message]
2006-08-21 7:04 ` 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=1156019429.3726.18.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=aherrman@de.ibm.com \
--cc=axboe@suse.de \
--cc=jejb@SteelEye.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®