From: Mikel Astiz <mikel.astiz.oss@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Mikel Astiz <mikel.astiz@bmw-carit.de>
Subject: [PATCH obexd v2 5/8] client: terminate queued transfers properly
Date: Tue, 21 Feb 2012 14:57:09 +0100 [thread overview]
Message-ID: <1329832632-3681-6-git-send-email-mikel.astiz.oss@gmail.com> (raw)
In-Reply-To: <1329832632-3681-1-git-send-email-mikel.astiz.oss@gmail.com>
From: Mikel Astiz <mikel.astiz@bmw-carit.de>
Previous implementation of session_terminate_transfer assumed that the
transfer being terminated would always be the active one. However, it
should be possible to cancel any queued transfer using the D-Bus api.
---
client/session.c | 27 +++++++++++++++++++++++----
1 files changed, 23 insertions(+), 4 deletions(-)
diff --git a/client/session.c b/client/session.c
index 7f387d4..3429f0a 100644
--- a/client/session.c
+++ b/client/session.c
@@ -764,14 +764,31 @@ static void session_process_queue(struct obc_session *session)
obc_session_unref(session);
}
+static gint pending_transfer_cmptransfer(gconstpointer a, gconstpointer b)
+{
+ const struct pending_request *p = a;
+ const struct obc_transfer *transfer = b;
+
+ return p->transfer < transfer ? -1 : (p->transfer > transfer ? 1 : 0);
+}
+
static void session_terminate_transfer(struct obc_session *session,
struct obc_transfer *transfer,
GError *gerr)
{
struct pending_request *p = session->p;
- if (p == NULL || p->transfer != transfer)
- return;
+ if (p == NULL || p->transfer != transfer) {
+ GList *match;
+
+ match = g_list_find_custom(session->queue->head, transfer,
+ pending_transfer_cmptransfer);
+ if (match == NULL)
+ return;
+
+ p = match->data;
+ g_queue_delete_link(session->queue, match);
+ }
obc_session_ref(session);
@@ -779,9 +796,11 @@ static void session_terminate_transfer(struct obc_session *session,
p->func(session, gerr, p->data);
pending_request_free(p);
- session->p = NULL;
- session_process_queue(session);
+ if (p == session->p) {
+ session->p = NULL;
+ session_process_queue(session);
+ }
obc_session_unref(session);
}
--
1.7.6.5
next prev parent reply other threads:[~2012-02-21 13:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 13:57 [PATCH obexd v2 0/8] Transfer cancelation Mikel Astiz
2012-02-21 13:57 ` [PATCH obexd v2 1/8] gobex: fix callback remove when canceling transfer Mikel Astiz
2012-02-21 13:57 ` [PATCH obexd v2 2/8] client: fix obc_session_get_buffer Mikel Astiz
2012-02-21 13:57 ` [PATCH obexd v2 3/8] client: fix cancel when no agent present Mikel Astiz
2012-02-21 13:57 ` [PATCH obexd v2 4/8] client: process transfer queue only if none active Mikel Astiz
2012-02-21 13:57 ` Mikel Astiz [this message]
2012-02-26 17:23 ` [PATCH obexd v2 5/8] client: terminate queued transfers properly Johan Hedberg
2012-02-21 13:57 ` [PATCH obexd v2 6/8] client: expose obc_transfer_set_callback Mikel Astiz
2012-02-21 13:57 ` [PATCH obexd v2 7/8] client: fix canceling queued transfers Mikel Astiz
2012-02-22 11:41 ` Jaganath
2012-02-22 11:59 ` Jaganath
2012-02-22 12:15 ` Luiz Augusto von Dentz
2012-02-22 12:24 ` Jaganath
2012-02-22 12:39 ` Luiz Augusto von Dentz
2012-02-26 17:26 ` Johan Hedberg
2012-02-21 13:57 ` [PATCH obexd v2 8/8] client: make sure callback does not match size Mikel Astiz
2012-02-24 9:33 ` [PATCH obexd v2 0/8] Transfer cancelation Luiz Augusto von Dentz
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=1329832632-3681-6-git-send-email-mikel.astiz.oss@gmail.com \
--to=mikel.astiz.oss@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mikel.astiz@bmw-carit.de \
/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;
as well as URLs for NNTP newsgroup(s).