From: "Justin T. Gibbs" <Justin_Gibbs@adaptec.com>
To: arjanv@redhat.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] 2.4.X Avoid excessive recursion when setting device offline
Date: Mon, 29 Mar 2004 10:42:19 -0700 [thread overview]
Message-ID: <412520000.1080582139@aslan.btc.adaptec.com> (raw)
In-Reply-To: <1080581208.3570.10.camel@laptop.fenrus.com>
>> This patch prevents recursive calls through the scsi_request_fn
>> for the same queue:
>
> won't this achieve the same ?
Yes, it appears it will and that the latest 2.4.X kernels already
have this change. My only concern stems from the need to audit all
of the callers of __scsi_end_request to ensure they are setting
the frequeue flag correctly.
--
Justin
next prev parent reply other threads:[~2004-03-29 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 17:07 [PATCH] 2.4.X Avoid excessive recursion when setting device offline Justin T. Gibbs
2004-03-29 17:26 ` Arjan van de Ven
2004-03-29 17:42 ` Justin T. Gibbs [this message]
2004-03-29 17:47 ` James Bottomley
2004-03-29 17:52 ` Justin T. Gibbs
2004-03-30 7:03 ` 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=412520000.1080582139@aslan.btc.adaptec.com \
--to=justin_gibbs@adaptec.com \
--cc=arjanv@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox