Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 2/3] stkutil: add missing text and icon check
Date: Tue, 04 Jan 2011 10:43:33 -0600	[thread overview]
Message-ID: <4D234E35.8070109@gmail.com> (raw)
In-Reply-To: <1293798647-4256-3-git-send-email-jeevaka.badrappan@elektrobit.com>

[-- Attachment #1: Type: text/plain, Size: 2452 bytes --]

Hi Jeevaka,

On 12/31/2010 06:30 AM, Jeevaka Badrappan wrote:
> As per the ETSI TS 102 223 section 6.5.4,
> If the terminalreceives an icon, and
> either an empty or no alpha identifier/text
> string is given by the UICC, than the terminal
> shall reject the command with general result
> "Command data not understood by terminal".
> ---
>  src/stkutil.c |  187 ++++++++++++++++++++++++++++++++++++++++++++++++++++-----
>  1 files changed, 171 insertions(+), 16 deletions(-)
> 
> diff --git a/src/stkutil.c b/src/stkutil.c
> index 8aee8f7..28d0a86 100644
> --- a/src/stkutil.c
> +++ b/src/stkutil.c
> @@ -74,6 +74,14 @@ struct gsm_sms_tpdu {
>  	unsigned char tpdu[184];
>  };
>  
> +static gboolean check_text_and_icon( const char *in, const unsigned char icon_id)

Why is there a space before const char?

> +{
> +	if ((in == NULL || strlen(in) < 1) && icon_id != 0)

Can in ever be null?  And I'd also prefer not using strlen(in) but using
in[0] == '\0'.

> +		return FALSE;
> +
> +	return TRUE;
> +}
> +
>  static char *decode_text(unsigned char dcs, int len, const unsigned char *data)
>  {
>  	char *utf8;
> @@ -2383,6 +2391,7 @@ static enum stk_command_parse_result parse_display_text(
>  					struct comprehension_tlv_iter *iter)
>  {
>  	struct stk_command_display_text *obj = &command->display_text;
> +	enum stk_command_parse_result result;
>  
>  	if (command->src != STK_DEVICE_IDENTITY_TYPE_UICC)
>  		return STK_PARSE_RESULT_DATA_NOT_UNDERSTOOD;
> @@ -2392,7 +2401,7 @@ static enum stk_command_parse_result parse_display_text(
>  
>  	command->destructor = destroy_display_text;
>  
> -	return parse_dataobj(iter, STK_DATA_OBJECT_TYPE_TEXT,
> +	result = parse_dataobj(iter, STK_DATA_OBJECT_TYPE_TEXT,
>  				DATAOBJ_FLAG_MANDATORY | DATAOBJ_FLAG_MINIMUM,
>  				&obj->text,
>  				STK_DATA_OBJECT_TYPE_ICON_ID, 0,
> @@ -2406,6 +2415,14 @@ static enum stk_command_parse_result parse_display_text(
>  				STK_DATA_OBJECT_TYPE_FRAME_ID, 0,
>  				&obj->frame_id,
>  				STK_DATA_OBJECT_TYPE_INVALID);
> +
> +	if (result != STK_PARSE_RESULT_OK)
> +		return result;
> +
> +	if (check_text_and_icon(obj->text, obj->icon_id.id) == FALSE)
> +		result = STK_PARSE_RESULT_DATA_NOT_UNDERSTOOD;
> +
> +	return result;
>  }
>  

Since the following code is repeated ad-naseum, I'd like to see this as
a macro.  See e.g. CALLBACK_END macro in src/stkagent.c

Regards,
-Denis

  reply	other threads:[~2011-01-04 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-31 12:30 [PATCH 0/3] Add null text/alpha identifier and icon check handling Jeevaka Badrappan
2010-12-31 12:30 ` [PATCH 1/3] stkutil: Allocate for empty string in text dataobj Jeevaka Badrappan
2010-12-31 12:30 ` [PATCH 2/3] stkutil: add missing text and icon check Jeevaka Badrappan
2011-01-04 16:43   ` Denis Kenzior [this message]
2011-01-04 22:11     ` Jeevaka Badrappan
2010-12-31 12:30 ` [PATCH 3/3] unit: add error status support for failure cases Jeevaka Badrappan

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=4D234E35.8070109@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