>> The mutex was (and is still only) locked within case branches, isn't it?
>>
> You are correct, this does however reflect the issue with the resulting
> lack of balance here.
Do you find changes for the other function implementations easier to integrate?
Regards,
Markus
>> The mutex was (and is still only) locked within case branches, isn't it?
>>
> You are correct, this does however reflect the issue with the resulting
> lack of balance here.
Do you find changes for the other function implementations easier to integrate?
Regards,
Markus
>> The mutex was (and is still only) locked within case branches, isn't it?
>>
> You are correct, this does however reflect the issue with the resulting
> lack of balance here.
I suggest to reconsider affected software aspects a bit more.
> I saw the mutex was getting unlocked outside the local
>> The mutex was (and is still only) locked within case branches, isn't it?
>>
> You are correct, this does however reflect the issue with the resulting
> lack of balance here.
I suggest to reconsider affected software aspects a bit more.
> I saw the mutex was getting unlocked outside the local
On Sun, 18 Mar 2018 09:19:47 +0100
SF Markus Elfring wrote:
> Am 17.03.2018 um 20:54 schrieb Jonathan Cameron:
> > On Wed, 14 Mar 2018 16:15:32 +0100
> > SF Markus Elfring wrote:
> >
> >> From: Markus Elfring
On Sun, 18 Mar 2018 09:19:47 +0100
SF Markus Elfring wrote:
> Am 17.03.2018 um 20:54 schrieb Jonathan Cameron:
> > On Wed, 14 Mar 2018 16:15:32 +0100
> > SF Markus Elfring wrote:
> >
> >> From: Markus Elfring
> >> Date: Wed, 14 Mar 2018 16:06:49 +0100
> >>
> >> * Add jump targets so that a
On Sat, Mar 17, 2018 at 07:54:22PM +, Jonathan Cameron wrote:
> On Wed, 14 Mar 2018 16:15:32 +0100
> SF Markus Elfring wrote:
>
> > From: Markus Elfring
> > Date: Wed, 14 Mar 2018 16:06:49 +0100
> >
> > * Add jump targets so
On Sat, Mar 17, 2018 at 07:54:22PM +, Jonathan Cameron wrote:
> On Wed, 14 Mar 2018 16:15:32 +0100
> SF Markus Elfring wrote:
>
> > From: Markus Elfring
> > Date: Wed, 14 Mar 2018 16:06:49 +0100
> >
> > * Add jump targets so that a call of the function "mutex_unlock" is stored
> > only
Am 17.03.2018 um 20:54 schrieb Jonathan Cameron:
> On Wed, 14 Mar 2018 16:15:32 +0100
> SF Markus Elfring wrote:
>
>> From: Markus Elfring
>> Date: Wed, 14 Mar 2018 16:06:49 +0100
>>
>> * Add jump targets so that a call of the
Am 17.03.2018 um 20:54 schrieb Jonathan Cameron:
> On Wed, 14 Mar 2018 16:15:32 +0100
> SF Markus Elfring wrote:
>
>> From: Markus Elfring
>> Date: Wed, 14 Mar 2018 16:06:49 +0100
>>
>> * Add jump targets so that a call of the function "mutex_unlock" is stored
>> only once in these function
On Wed, 14 Mar 2018 16:15:32 +0100
SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 14 Mar 2018 16:06:49 +0100
>
> * Add jump targets so that a call of the function "mutex_unlock" is stored
> only once in these
On Wed, 14 Mar 2018 16:15:32 +0100
SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 14 Mar 2018 16:06:49 +0100
>
> * Add jump targets so that a call of the function "mutex_unlock" is stored
> only once in these function implementations.
>
> * Replace 19 calls by goto statements.
From: Markus Elfring
Date: Wed, 14 Mar 2018 16:06:49 +0100
* Add jump targets so that a call of the function "mutex_unlock" is stored
only once in these function implementations.
* Replace 19 calls by goto statements.
This issue was detected by using the
From: Markus Elfring
Date: Wed, 14 Mar 2018 16:06:49 +0100
* Add jump targets so that a call of the function "mutex_unlock" is stored
only once in these function implementations.
* Replace 19 calls by goto statements.
This issue was detected by using the Coccinelle software.
Signed-off-by:
14 matches
Mail list logo