From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] fix ofonod crash when pin is blocked
Date: Wed, 11 Sep 2013 13:01:10 -0500 [thread overview]
Message-ID: <5230AFE6.6050204@gmail.com> (raw)
In-Reply-To: <1378919634-5912-1-git-send-email-caiwen.zhang@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
Hi Caiwen,
On 09/11/2013 12:13 PM, caiwen.zhang(a)intel.com wrote:
> From: Caiwen Zhang <caiwen.zhang@intel.com>
>
> When is blocked, gprs/network atom is removed, it will
> remove the SIM SPN watch which is added when it is created.
> If at that time, SIM atom has been removed ofonod will crash
> due to "sim->spn_watches" is NULL.
>
This description makes no sense. The SIM atom is never removed due to a
blocked PIN, so can you please provide a more clear description of the
issue?
> There is the same issue about network registration status watch.
> ---
> src/watch.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/src/watch.c b/src/watch.c
> index dfb01fb..906c559 100644
> --- a/src/watch.c
> +++ b/src/watch.c
> @@ -53,6 +53,9 @@ gboolean __ofono_watchlist_remove_item(struct ofono_watchlist *watchlist,
> GSList *p;
> GSList *c;
>
> + if (watchlist == NULL)
> + return;
> +
This fix is wrong, you're likely just covering up the symptom, not the
cause. oFono operates on the principle of crash-early, so that bugs are
easier to detect and find.
What is the real reason why the watchlist is NULL at the point in time
this function is being called?
> p = NULL;
> c = watchlist->items;
>
>
Regards,
-Denis
next prev parent reply other threads:[~2013-09-11 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 17:13 [PATCH] fix ofonod crash when pin is blocked caiwen.zhang
2013-09-11 18:01 ` Denis Kenzior [this message]
2013-09-12 0:53 ` Zhang, Caiwen
2013-09-12 13:28 ` 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=5230AFE6.6050204@gmail.com \
--to=denkenz@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox