All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] android/gatt: Fix wrong initial value
@ 2014-06-12 10:43 Andrei Emeltchenko
  2014-06-12 11:05 ` Marcin Kraglak
  0 siblings, 1 reply; 4+ messages in thread
From: Andrei Emeltchenko @ 2014-06-12 10:43 UTC (permalink / raw)
  To: linux-bluetooth

From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>

Initialize value_len to -1 since otherwise check value_len >= 0 does not
make sense.
---
 android/gatt.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/android/gatt.c b/android/gatt.c
index 8da77d0..8260a8d 100644
--- a/android/gatt.c
+++ b/android/gatt.c
@@ -4147,7 +4147,7 @@ static void read_requested_attributes(void *data, void *user_data)
 	struct request_processing_data *process_data = user_data;
 	uint32_t permissions;
 	uint8_t *value, error;
-	int value_len = 0;
+	int value_len = -1;
 
 	if (!gatt_db_get_attribute_permissions(gatt_db, resp_data->handle,
 								&permissions)) {
-- 
1.8.3.2


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH] android/gatt: Fix wrong initial value
  2014-06-12 10:43 [PATCH] android/gatt: Fix wrong initial value Andrei Emeltchenko
@ 2014-06-12 11:05 ` Marcin Kraglak
  2014-06-12 11:22   ` Andrei Emeltchenko
  0 siblings, 1 reply; 4+ messages in thread
From: Marcin Kraglak @ 2014-06-12 11:05 UTC (permalink / raw)
  To: Andrei Emeltchenko; +Cc: linux-bluetooth@vger.kernel.org development

Hi Andrei,

On 12 June 2014 12:43, Andrei Emeltchenko
<Andrei.Emeltchenko.news@gmail.com> wrote:
> From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
>
> Initialize value_len to -1 since otherwise check value_len >= 0 does not
> make sense.
> ---
>  android/gatt.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/android/gatt.c b/android/gatt.c
> index 8da77d0..8260a8d 100644
> --- a/android/gatt.c
> +++ b/android/gatt.c
> @@ -4147,7 +4147,7 @@ static void read_requested_attributes(void *data, void *user_data)
>         struct request_processing_data *process_data = user_data;
>         uint32_t permissions;
>         uint8_t *value, error;
> -       int value_len = 0;
> +       int value_len = -1;

What will happen if check_device_permissions will fail?
>
>         if (!gatt_db_get_attribute_permissions(gatt_db, resp_data->handle,
>                                                                 &permissions)) {
> --
> 1.8.3.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

BR
Marcin

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] android/gatt: Fix wrong initial value
  2014-06-12 11:05 ` Marcin Kraglak
@ 2014-06-12 11:22   ` Andrei Emeltchenko
  2014-06-12 11:24     ` Marcin Kraglak
  0 siblings, 1 reply; 4+ messages in thread
From: Andrei Emeltchenko @ 2014-06-12 11:22 UTC (permalink / raw)
  To: Marcin Kraglak; +Cc: linux-bluetooth@vger.kernel.org development

On Thu, Jun 12, 2014 at 01:05:45PM +0200, Marcin Kraglak wrote:
> Hi Andrei,
> 
> On 12 June 2014 12:43, Andrei Emeltchenko
> <Andrei.Emeltchenko.news@gmail.com> wrote:
> > From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> >
> > Initialize value_len to -1 since otherwise check value_len >= 0 does not
> > make sense.
> > ---
> >  android/gatt.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/android/gatt.c b/android/gatt.c
> > index 8da77d0..8260a8d 100644
> > --- a/android/gatt.c
> > +++ b/android/gatt.c
> > @@ -4147,7 +4147,7 @@ static void read_requested_attributes(void *data, void *user_data)
> >         struct request_processing_data *process_data = user_data;
> >         uint32_t permissions;
> >         uint8_t *value, error;
> > -       int value_len = 0;
> > +       int value_len = -1;
> 
> What will happen if check_device_permissions will fail?

nothing? Should we send message?

Best regards 
Andrei Emeltchenko 


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] android/gatt: Fix wrong initial value
  2014-06-12 11:22   ` Andrei Emeltchenko
@ 2014-06-12 11:24     ` Marcin Kraglak
  0 siblings, 0 replies; 4+ messages in thread
From: Marcin Kraglak @ 2014-06-12 11:24 UTC (permalink / raw)
  To: Andrei Emeltchenko, Marcin Kraglak,
	linux-bluetooth@vger.kernel.org development

Hi,

On 12 June 2014 13:22, Andrei Emeltchenko
<Andrei.Emeltchenko.news@gmail.com> wrote:
> On Thu, Jun 12, 2014 at 01:05:45PM +0200, Marcin Kraglak wrote:
>> Hi Andrei,
>>
>> On 12 June 2014 12:43, Andrei Emeltchenko
>> <Andrei.Emeltchenko.news@gmail.com> wrote:
>> > From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
>> >
>> > Initialize value_len to -1 since otherwise check value_len >= 0 does not
>> > make sense.
>> > ---
>> >  android/gatt.c | 2 +-
>> >  1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/android/gatt.c b/android/gatt.c
>> > index 8da77d0..8260a8d 100644
>> > --- a/android/gatt.c
>> > +++ b/android/gatt.c
>> > @@ -4147,7 +4147,7 @@ static void read_requested_attributes(void *data, void *user_data)
>> >         struct request_processing_data *process_data = user_data;
>> >         uint32_t permissions;
>> >         uint8_t *value, error;
>> > -       int value_len = 0;
>> > +       int value_len = -1;
>>
>> What will happen if check_device_permissions will fail?
>
> nothing? Should we send message?

we should set error in resp_data. Anyway it is repaired in
android/gatt: Set state of pending responses


>
> Best regards
> Andrei Emeltchenko
>

BR
Marcin

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2014-06-12 11:24 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-06-12 10:43 [PATCH] android/gatt: Fix wrong initial value Andrei Emeltchenko
2014-06-12 11:05 ` Marcin Kraglak
2014-06-12 11:22   ` Andrei Emeltchenko
2014-06-12 11:24     ` Marcin Kraglak

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.