From: David Disseldorp <ddiss@suse.de>
To: target-devel@vger.kernel.org
Subject: Re: [PATCH] target/core: Avoid that a kernel oops can be triggered when an XCOPY command fails
Date: Mon, 05 Nov 2018 19:09:14 +0000 [thread overview]
Message-ID: <20181105200914.7607f159@suse.de> (raw)
In-Reply-To: <20181105184011.94041-1-bvanassche@acm.org>
On Mon, 5 Nov 2018 10:40:11 -0800, Bart Van Assche wrote:
> Fixes: aa73237dcb2d ("scsi: target/core: Always call transport_complete_callback() upon failure")
> Cc: Nicholas Bellinger <nab@linux-iscsi.org>
> Cc: David Disseldorp <ddiss@suse.de>
> Cc: Mike Christie <mchristi@redhat.com>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Hannes Reinecke <hare@suse.de>
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> ---
> drivers/target/target_core_transport.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/target/target_core_transport.c b/drivers/target/target_core_transport.c
> index e31e4fc31aa1..2cfd61d62e97 100644
> --- a/drivers/target/target_core_transport.c
> +++ b/drivers/target/target_core_transport.c
> @@ -1778,7 +1778,7 @@ EXPORT_SYMBOL(target_submit_tmr);
> void transport_generic_request_failure(struct se_cmd *cmd,
> sense_reason_t sense_reason)
> {
> - int ret = 0;
> + int ret = 0, post_ret;
>
> pr_debug("-----[ Storage Engine Exception; sense_reason %d\n",
> sense_reason);
> @@ -1790,7 +1790,7 @@ void transport_generic_request_failure(struct se_cmd *cmd,
> transport_complete_task_attr(cmd);
>
> if (cmd->transport_complete_callback)
> - cmd->transport_complete_callback(cmd, false, NULL);
> + cmd->transport_complete_callback(cmd, false, &post_ret);
>
> if (transport_check_aborted_status(cmd, 1))
> return;
Reviewed-by: David Disseldorp <ddiss@suse.de>
next prev parent reply other threads:[~2018-11-05 19:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 18:40 [PATCH] target/core: Avoid that a kernel oops can be triggered when an XCOPY command fails Bart Van Assche
2018-11-05 19:09 ` David Disseldorp [this message]
2018-11-05 23:19 ` David Disseldorp
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=20181105200914.7607f159@suse.de \
--to=ddiss@suse.de \
--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.