From: Slava Monich <slava.monich@jolla.com>
To: ofono@ofono.org
Subject: Re: [PATCH] sim: Handle multiple invocations of sim_imsi_obtained
Date: Tue, 06 May 2014 17:22:07 +0300 [thread overview]
Message-ID: <5368F00F.5040609@jolla.com> (raw)
In-Reply-To: <5368E5EA.8070409@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]
Hi Denis,
>> To avoid leaking memory and issuing unnecessary D-Bus signals
>> ---
>> src/sim.c | 11 +++++++++--
>> 1 file changed, 9 insertions(+), 2 deletions(-)
>>
>> diff --git a/src/sim.c b/src/sim.c
>> index edae5eb..1b0cb80 100644
>> --- a/src/sim.c
>> +++ b/src/sim.c
>> @@ -1425,11 +1425,18 @@ static void sim_set_ready(struct ofono_sim *sim)
>>
>> static void sim_imsi_obtained(struct ofono_sim *sim, const char *imsi)
>> {
>> - DBusConnection *conn = ofono_dbus_get_connection();
>> - const char *path = __ofono_atom_get_path(sim->atom);
>> + DBusConnection *conn;
>> + const char *path;
>> +
>> + if (sim->imsi && !strcmp(sim->imsi, imsi))
>> + return;
> Calling this function a second time is an error. So this condition
> looks highly suspect. What issue are you trying to address?
sim_imsi_obtained() is invoked from two places: sim_imsi_cb() and
sim_efimsi_cb(). sim_imsi_cb() in turn is a completion for
sim_retrieve_imsi() which is invoked from 5 other asynchronous
callbacks, mostly triggered by a number of ofono_sim_read() calls. I
don't claim that I fully understand what's going on and I haven't
analyzed all the call sequences but it surely is invoked twice in our
setup. Any suggestions on where the problem might be?
Thanks,
-Slava
next prev parent reply other threads:[~2014-05-06 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 11:54 [PATCH] sim: Handle multiple invocations of sim_imsi_obtained Slava Monich
2014-05-06 13:38 ` Denis Kenzior
2014-05-06 14:22 ` Slava Monich [this message]
2014-05-06 20:59 ` Denis Kenzior
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=5368F00F.5040609@jolla.com \
--to=slava.monich@jolla.com \
--cc=ofono@ofono.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.