From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Bart Van Assche <Bart.VanAssche@sandisk.com>
Cc: "target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v6 14/33] target: Avoid that target drivers hang if a command is aborted
Date: Wed, 01 Mar 2017 23:02:00 -0800 [thread overview]
Message-ID: <1488438120.21712.70.camel@haakon3.risingtidesystems.com> (raw)
In-Reply-To: <1488432232.3505.6.camel@sandisk.com>
On Thu, 2017-03-02 at 05:24 +0000, Bart Van Assche wrote:
> On Wed, 2017-03-01 at 21:21 -0800, Nicholas A. Bellinger wrote:
> > To reiterate the importance of having bug-fixes, especially those
> > intended for stable, always be leading other patches..
>
> You should know that I can't group all bugfixes at the start of the series
> because some of the bugfixes depend on patches that are not bugfixes.
>
That makes no sense. Either it's a bug-fix to existing upstream code,
or it's not.
This patch was not a bug-fix to upstream, because it detailed a scenario
that doesn't existing in upstream. That is, a case where ib_isert or
ib_srpt calls target_generic_free_cmd() with wait_for_tasks = true or a
case where wait_for_tasks = false blocks.
next prev parent reply other threads:[~2017-03-02 7:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170215002612.14566-1-bart.vanassche@sandisk.com>
2017-02-15 0:25 ` [PATCH v6 14/33] target: Avoid that target drivers hang if a command is aborted Bart Van Assche
2017-02-20 21:38 ` Nicholas A. Bellinger
2017-02-21 18:58 ` Bart Van Assche
2017-03-02 5:21 ` Nicholas A. Bellinger
2017-03-02 5:24 ` Bart Van Assche
2017-03-02 7:02 ` Nicholas A. Bellinger [this message]
2017-02-15 0:25 ` [PATCH v6 15/33] target: Avoid circular waits between LUN resets Bart Van Assche
2017-02-20 22:32 ` Nicholas A. Bellinger
2017-02-15 0:25 ` [PATCH v6 19/33] target: Avoid that LUN reset sporadically triggers data corruption Bart Van Assche
2017-02-20 23:52 ` Nicholas A. Bellinger
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=1488438120.21712.70.camel@haakon3.risingtidesystems.com \
--to=nab@linux-iscsi.org \
--cc=Bart.VanAssche@sandisk.com \
--cc=stable@vger.kernel.org \
--cc=target-devel@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.