In futex_lock_pi(), after rt_mutex_timed_lock() fails, the followed
fixup_owner() still may return 0 to express "success, lock not taken"
(may printk kernel error in it).
When it happens, 'res' is zero, 'ret' is still none-zero, and
"rt_mutex_owner(_state->pi_mutex) == current", it will call
In futex_lock_pi(), after rt_mutex_timed_lock() fails, the followed
fixup_owner() still may return 0 to express success, lock not taken
(may printk kernel error in it).
When it happens, 'res' is zero, 'ret' is still none-zero, and
rt_mutex_owner(q.pi_state-pi_mutex) == current, it will call
After read the code again, I have addtional opinion for discussing,
please check thanks.
The related contents are at bottom.
On 09/13/2013 09:52 AM, Chen Gang wrote:
> On 09/13/2013 07:36 AM, Thomas Gleixner wrote:
>> That crusade does not involve any failure analysis or test cases. It's
>>
After read the code again, I have addtional opinion for discussing,
please check thanks.
The related contents are at bottom.
On 09/13/2013 09:52 AM, Chen Gang wrote:
On 09/13/2013 07:36 AM, Thomas Gleixner wrote:
That crusade does not involve any failure analysis or test cases. It's
just
Firstly, I am glad to see that you did not redirect all my mails to
"/dev/null". ;-)
On 09/13/2013 07:36 AM, Thomas Gleixner wrote:
> On Thu, 12 Sep 2013, Darren Hart wrote:
>> On Thu, 2013-09-12 at 16:32 +0200, Thomas Gleixner wrote:
>>> On Tue, 20 Aug 2013, Chen Gang wrote:
>>>
On 09/13/2013 06:37 AM, Darren Hart wrote:
> On Thu, 2013-09-12 at 16:32 +0200, Thomas Gleixner wrote:
>> On Tue, 20 Aug 2013, Chen Gang wrote:
>>
>>> rt_mutex_finish_proxy_lock() can return failure code (e.g. -EINTR,
>>> -ETIMEDOUT).
>>>
>>> Original implementation has already noticed about it,
On Thu, 12 Sep 2013, Darren Hart wrote:
> On Thu, 2013-09-12 at 16:32 +0200, Thomas Gleixner wrote:
> > On Tue, 20 Aug 2013, Chen Gang wrote:
> >
> > > rt_mutex_finish_proxy_lock() can return failure code (e.g. -EINTR,
> > > -ETIMEDOUT).
> > >
> > > Original implementation has already noticed
On Thu, 2013-09-12 at 16:32 +0200, Thomas Gleixner wrote:
> On Tue, 20 Aug 2013, Chen Gang wrote:
>
> > rt_mutex_finish_proxy_lock() can return failure code (e.g. -EINTR,
> > -ETIMEDOUT).
> >
> > Original implementation has already noticed about it, but not check it
> > before next work.
> >
>
On Tue, 20 Aug 2013, Chen Gang wrote:
> rt_mutex_finish_proxy_lock() can return failure code (e.g. -EINTR,
> -ETIMEDOUT).
>
> Original implementation has already noticed about it, but not check it
> before next work.
>
> Also let coments within 80 columns to pass "./scripts/checkpatch.pl".
>
>
On Tue, 20 Aug 2013, Chen Gang wrote:
rt_mutex_finish_proxy_lock() can return failure code (e.g. -EINTR,
-ETIMEDOUT).
Original implementation has already noticed about it, but not check it
before next work.
Also let coments within 80 columns to pass ./scripts/checkpatch.pl.
On Thu, 2013-09-12 at 16:32 +0200, Thomas Gleixner wrote:
On Tue, 20 Aug 2013, Chen Gang wrote:
rt_mutex_finish_proxy_lock() can return failure code (e.g. -EINTR,
-ETIMEDOUT).
Original implementation has already noticed about it, but not check it
before next work.
Also let
On Thu, 12 Sep 2013, Darren Hart wrote:
On Thu, 2013-09-12 at 16:32 +0200, Thomas Gleixner wrote:
On Tue, 20 Aug 2013, Chen Gang wrote:
rt_mutex_finish_proxy_lock() can return failure code (e.g. -EINTR,
-ETIMEDOUT).
Original implementation has already noticed about it, but not
On 09/13/2013 06:37 AM, Darren Hart wrote:
On Thu, 2013-09-12 at 16:32 +0200, Thomas Gleixner wrote:
On Tue, 20 Aug 2013, Chen Gang wrote:
rt_mutex_finish_proxy_lock() can return failure code (e.g. -EINTR,
-ETIMEDOUT).
Original implementation has already noticed about it, but not check it
Firstly, I am glad to see that you did not redirect all my mails to
/dev/null. ;-)
On 09/13/2013 07:36 AM, Thomas Gleixner wrote:
On Thu, 12 Sep 2013, Darren Hart wrote:
On Thu, 2013-09-12 at 16:32 +0200, Thomas Gleixner wrote:
On Tue, 20 Aug 2013, Chen Gang wrote:
Hello Maintainers:
Please help check this patch, when you have time.
Thanks.
On 08/21/2013 11:48 AM, Chen Gang wrote:
> On 08/21/2013 12:19 AM, Darren Hart wrote:
>> HopingOn Tue, 2013-08-20 at 11:07 +0800, Chen Gang wrote:
>>
>>
>> Hi Chen,
>>
>>> rt_mutex_finish_proxy_lock() can return
Hello Maintainers:
Please help check this patch, when you have time.
Thanks.
On 08/21/2013 11:48 AM, Chen Gang wrote:
On 08/21/2013 12:19 AM, Darren Hart wrote:
HopingOn Tue, 2013-08-20 at 11:07 +0800, Chen Gang wrote:
Hi Chen,
rt_mutex_finish_proxy_lock() can return failure code (e.g.
On 08/21/2013 12:19 AM, Darren Hart wrote:
> HopingOn Tue, 2013-08-20 at 11:07 +0800, Chen Gang wrote:
>
>
> Hi Chen,
>
>> rt_mutex_finish_proxy_lock() can return failure code (e.g. -EINTR,
>> -ETIMEDOUT).
>>
>> Original implementation has already noticed about it, but not check it
>> before
HopingOn Tue, 2013-08-20 at 11:07 +0800, Chen Gang wrote:
Hi Chen,
> rt_mutex_finish_proxy_lock() can return failure code (e.g. -EINTR,
> -ETIMEDOUT).
>
> Original implementation has already noticed about it, but not check it
> before next work.
>
> Also let coments within 80 columns to pass
HopingOn Tue, 2013-08-20 at 11:07 +0800, Chen Gang wrote:
Hi Chen,
rt_mutex_finish_proxy_lock() can return failure code (e.g. -EINTR,
-ETIMEDOUT).
Original implementation has already noticed about it, but not check it
before next work.
Also let coments within 80 columns to pass
On 08/21/2013 12:19 AM, Darren Hart wrote:
HopingOn Tue, 2013-08-20 at 11:07 +0800, Chen Gang wrote:
Hi Chen,
rt_mutex_finish_proxy_lock() can return failure code (e.g. -EINTR,
-ETIMEDOUT).
Original implementation has already noticed about it, but not check it
before next work.
Also
rt_mutex_finish_proxy_lock() can return failure code (e.g. -EINTR,
-ETIMEDOUT).
Original implementation has already noticed about it, but not check it
before next work.
Also let coments within 80 columns to pass "./scripts/checkpatch.pl".
Signed-off-by: Chen Gang
---
kernel/futex.c | 30
rt_mutex_finish_proxy_lock() can return failure code (e.g. -EINTR,
-ETIMEDOUT).
Original implementation has already noticed about it, but not check it
before next work.
Also let coments within 80 columns to pass ./scripts/checkpatch.pl.
Signed-off-by: Chen Gang gang.c...@asianux.com
---
22 matches
Mail list logo