From: Grant Erickson <gerickson@nuovations.com>
To: connman@lists.linux.dev
Subject: [PATCH 0/2] ofono: Correct conditional in 'cm_get_contexts_reply'.
Date: Fri, 7 Feb 2025 17:01:56 -0800 [thread overview]
Message-ID: <cover.1738976381.git.gerickson@nuovations.com> (raw)
At the appropriate moment in the oFono plugin lifecycle, it gets and
evaluates contexts from a given Cellular modem. Depending on the
HNI/MCC+MNC and the network operator, there may be one or more such
contexts, each with a different type.
Within 'cm_get_contexts_reply', each received context is iterated on,
evaluating each for the type 'internet' by calling
'add_cm_context'. If the context is not of type 'internet',
'cm_get_contexts_reply' should continue to iterate until all contexts
are exhausted or a matching context is found.
The return semantics of 'add_cm_context' are '-ENOMEM' if memory could
not be allocated, '-EINVAL' if a context is *not* of the type
'internet'; otherwise zero ('0') if a context of type 'internet' was
found.
However, the conditional logic of 'cm_get_contexts_reply' prior to
this change was:
while (dbus_message_iter_get_arg_type(&dict) == DBUS_TYPE_STRUCT) {
const char *context_path;
dbus_message_iter_recurse(&dict, &entry);
dbus_message_iter_get_basic(&entry, &context_path);
dbus_message_iter_next(&entry);
dbus_message_iter_recurse(&entry, &value);
if (add_cm_context(modem, context_path, &value))
break;
dbus_message_iter_next(&dict);
}
So, assuming a set of contexts from, for example Verizon, such as '[ {
vzwims, ims }, { vzwinternet, internet }, { vzwapp, wap } ]', then the
above logic will encounter '{ vzwims, ims }' on the first iteration,
evaluate that it is not of type 'internet', return '-EINVAL' from
'add_cm_context', that will satisfy the conditional and trigger the
'break' from the 'while' loop and context iteration will
terminate. This then misses the second, desired '{ vzwinternet,
internet }' context and the Cellular interface will never come up.
By changing the conditional logic to match the return semantics of
'add_cm_context' the code now works correctly, regardless of the number
of contexts iterated on or their order.
Grant Erickson (2):
ofono: Correct conditional in 'cm_get_contexts_reply'.
ofono: Document 'add_cm_context'.
plugins/ofono.c | 35 ++++++++++++++++++++++++++++++++++-
1 file changed, 34 insertions(+), 1 deletion(-)
--
2.45.0
next reply other threads:[~2025-02-08 1:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 1:01 Grant Erickson [this message]
2025-02-08 1:01 ` [PATCH 1/2] ofono: Correct conditional in 'cm_get_contexts_reply' Grant Erickson
2025-02-08 1:01 ` [PATCH 2/2] ofono: Document 'add_cm_context' Grant Erickson
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=cover.1738976381.git.gerickson@nuovations.com \
--to=gerickson@nuovations.com \
--cc=connman@lists.linux.dev \
/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