From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: [Qemu-devel] [PULL v1 5/8] io: add ability to associate an error with a task
Date: Mon, 23 Jan 2017 14:26:26 +0000 [thread overview]
Message-ID: <20170123142629.11110-6-berrange@redhat.com> (raw)
In-Reply-To: <20170123142629.11110-1-berrange@redhat.com>
Currently when a task fails, the error is never explicitly
associated with the task object, it is just passed along
through the completion callback. This adds the ability to
explicitly associate an error with the task.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
---
include/io/task.h | 32 ++++++++++++++++++++++++++++++++
io/task.c | 23 +++++++++++++++++++++++
2 files changed, 55 insertions(+)
diff --git a/include/io/task.h b/include/io/task.h
index ece1372..47daba9 100644
--- a/include/io/task.h
+++ b/include/io/task.h
@@ -240,6 +240,38 @@ void qio_task_abort(QIOTask *task,
/**
+ * qio_task_set_error:
+ * @task: the task struct
+ * @err: pointer to the error, or NULL
+ *
+ * Associate an error with the task, which can later
+ * be retrieved with the qio_task_propagate_error()
+ * method. This method takes ownership of @err, so
+ * it is not valid to access it after this call
+ * completes. If @err is NULL this is a no-op. If
+ * this is call multiple times, only the first
+ * provided @err will be recorded, later ones will
+ * be discarded and freed.
+ */
+void qio_task_set_error(QIOTask *task,
+ Error *err);
+
+
+/**
+ * qio_task_propagate_error:
+ * @task: the task struct
+ * @errp: pointer to a NULL-initialized error object
+ *
+ * Propagate the error associated with @task
+ * into @errp.
+ *
+ * Returns: true if an error was propagated, false otherwise
+ */
+bool qio_task_propagate_error(QIOTask *task,
+ Error **errp);
+
+
+/**
* qio_task_set_result_pointer:
* @task: the task struct
* @result: pointer to the result data
diff --git a/io/task.c b/io/task.c
index 675e196..1394e05 100644
--- a/io/task.c
+++ b/io/task.c
@@ -29,6 +29,7 @@ struct QIOTask {
QIOTaskFunc func;
gpointer opaque;
GDestroyNotify destroy;
+ Error *err;
gpointer result;
GDestroyNotify destroyResult;
};
@@ -62,6 +63,9 @@ static void qio_task_free(QIOTask *task)
if (task->destroyResult) {
task->destroyResult(task->result);
}
+ if (task->err) {
+ error_free(task->err);
+ }
object_unref(task->source);
g_free(task);
@@ -159,6 +163,25 @@ void qio_task_abort(QIOTask *task,
}
+void qio_task_set_error(QIOTask *task,
+ Error *err)
+{
+ error_propagate(&task->err, err);
+}
+
+
+bool qio_task_propagate_error(QIOTask *task,
+ Error **errp)
+{
+ if (task->err) {
+ error_propagate(errp, task->err);
+ return true;
+ }
+
+ return false;
+}
+
+
void qio_task_set_result_pointer(QIOTask *task,
gpointer result,
GDestroyNotify destroy)
--
2.9.3
next prev parent reply other threads:[~2017-01-23 14:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 14:26 [Qemu-devel] [PULL v1 0/8] Merge io/ 2017-01-23 Daniel P. Berrange
2017-01-23 14:26 ` [Qemu-devel] [PULL v1 1/8] sockets: add ability to disable DNS resolution for InetSocketAddress Daniel P. Berrange
2017-01-23 14:26 ` [Qemu-devel] [PULL v1 2/8] io: stop incrementing reference in qio_task_get_source Daniel P. Berrange
2017-01-23 14:26 ` [Qemu-devel] [PULL v1 3/8] io: fix typo in docs for QIOTask Daniel P. Berrange
2017-01-23 14:26 ` [Qemu-devel] [PULL v1 4/8] io: add ability to associate an opaque "result" with with a task Daniel P. Berrange
2017-01-23 14:26 ` Daniel P. Berrange [this message]
2017-01-23 14:26 ` [Qemu-devel] [PULL v1 6/8] io: change the QIOTask callback signature Daniel P. Berrange
2017-01-23 14:26 ` [Qemu-devel] [PULL v1 7/8] io: remove Error parameter from QIOTask thread worker Daniel P. Berrange
2017-01-23 14:26 ` [Qemu-devel] [PULL v1 8/8] io: introduce a DNS resolver API Daniel P. Berrange
2017-01-23 14:43 ` [Qemu-devel] [PULL v1 0/8] Merge io/ 2017-01-23 no-reply
2017-01-23 14:46 ` Peter Maydell
2017-01-23 15:24 ` Peter Maydell
2017-01-23 15:36 ` Daniel P. Berrange
2017-01-23 15:36 ` Daniel P. Berrange
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=20170123142629.11110-6-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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.