On Wed, Mar 25, 2015 at 5:21 AM, Ingo Molnar wrote:
>
> * Andy Lutomirski wrote:
>
>> On Tue, Mar 24, 2015 at 1:08 PM, Ingo Molnar wrote:
>> >
>> > * Andy Lutomirski wrote:
>> >
>> >> We currently have a race: if we're preempted during syscall exit, we
>> >> can fail to process syscall return
* Andy Lutomirski wrote:
> On Tue, Mar 24, 2015 at 1:08 PM, Ingo Molnar wrote:
> >
> > * Andy Lutomirski wrote:
> >
> >> We currently have a race: if we're preempted during syscall exit, we
> >> can fail to process syscall return work that is queued up while
> >> we're preempted in
* Andy Lutomirski l...@amacapital.net wrote:
On Tue, Mar 24, 2015 at 1:08 PM, Ingo Molnar mi...@kernel.org wrote:
* Andy Lutomirski l...@kernel.org wrote:
We currently have a race: if we're preempted during syscall exit, we
can fail to process syscall return work that is queued up
On Wed, Mar 25, 2015 at 5:21 AM, Ingo Molnar mi...@kernel.org wrote:
* Andy Lutomirski l...@amacapital.net wrote:
On Tue, Mar 24, 2015 at 1:08 PM, Ingo Molnar mi...@kernel.org wrote:
* Andy Lutomirski l...@kernel.org wrote:
We currently have a race: if we're preempted during syscall
On Tue, Mar 24, 2015 at 1:08 PM, Ingo Molnar wrote:
>
> * Andy Lutomirski wrote:
>
>> We currently have a race: if we're preempted during syscall exit, we
>> can fail to process syscall return work that is queued up while
>> we're preempted in ret_from_sys_call after checking ti.flags.
>>
>> Fix
* Andy Lutomirski wrote:
> We currently have a race: if we're preempted during syscall exit, we
> can fail to process syscall return work that is queued up while
> we're preempted in ret_from_sys_call after checking ti.flags.
>
> Fix it by disabling interrupts before checking ti.flags.
>
>
At Mon, 23 Mar 2015 12:32:54 -0700,
Andy Lutomirski wrote:
>
> We currently have a race: if we're preempted during syscall exit, we
> can fail to process syscall return work that is queued up while
> we're preempted in ret_from_sys_call after checking ti.flags.
>
> Fix it by disabling interrupts
At Mon, 23 Mar 2015 12:32:54 -0700,
Andy Lutomirski wrote:
We currently have a race: if we're preempted during syscall exit, we
can fail to process syscall return work that is queued up while
we're preempted in ret_from_sys_call after checking ti.flags.
Fix it by disabling interrupts
On Tue, Mar 24, 2015 at 1:08 PM, Ingo Molnar mi...@kernel.org wrote:
* Andy Lutomirski l...@kernel.org wrote:
We currently have a race: if we're preempted during syscall exit, we
can fail to process syscall return work that is queued up while
we're preempted in ret_from_sys_call after
* Andy Lutomirski l...@kernel.org wrote:
We currently have a race: if we're preempted during syscall exit, we
can fail to process syscall return work that is queued up while
we're preempted in ret_from_sys_call after checking ti.flags.
Fix it by disabling interrupts before checking
On Mon, Mar 23, 2015 at 12:27 PM, Andy Lutomirski wrote:
> On Mon, Mar 23, 2015 at 12:21 PM, Denys Vlasenko wrote:
>> On 03/23/2015 08:10 PM, Andy Lutomirski wrote:
>>> We currently have a race: if we're preempted during syscall exit, we
>>> can fail to process syscall return work that is queued
On Mon, Mar 23, 2015 at 12:21 PM, Denys Vlasenko wrote:
> On 03/23/2015 08:10 PM, Andy Lutomirski wrote:
>> We currently have a race: if we're preempted during syscall exit, we
>> can fail to process syscall return work that is queued up while
>> we're preempted in ret_from_sys_call after
On 03/23/2015 08:10 PM, Andy Lutomirski wrote:
> We currently have a race: if we're preempted during syscall exit, we
> can fail to process syscall return work that is queued up while
> we're preempted in ret_from_sys_call after checking ti.flags.
>
> Fix it by disabling interrupts before
We currently have a race: if we're preempted during syscall exit, we
can fail to process syscall return work that is queued up while
we're preempted in ret_from_sys_call after checking ti.flags.
Fix it by disabling interrupts before checking ti.flags.
Fixes: 96b6352c1271 x86_64, entry: Remove
On Mon, Mar 23, 2015 at 12:21 PM, Denys Vlasenko dvlas...@redhat.com wrote:
On 03/23/2015 08:10 PM, Andy Lutomirski wrote:
We currently have a race: if we're preempted during syscall exit, we
can fail to process syscall return work that is queued up while
we're preempted in ret_from_sys_call
On Mon, Mar 23, 2015 at 12:27 PM, Andy Lutomirski l...@amacapital.net wrote:
On Mon, Mar 23, 2015 at 12:21 PM, Denys Vlasenko dvlas...@redhat.com wrote:
On 03/23/2015 08:10 PM, Andy Lutomirski wrote:
We currently have a race: if we're preempted during syscall exit, we
can fail to process
We currently have a race: if we're preempted during syscall exit, we
can fail to process syscall return work that is queued up while
we're preempted in ret_from_sys_call after checking ti.flags.
Fix it by disabling interrupts before checking ti.flags.
Fixes: 96b6352c1271 x86_64, entry: Remove
On 03/23/2015 08:10 PM, Andy Lutomirski wrote:
We currently have a race: if we're preempted during syscall exit, we
can fail to process syscall return work that is queued up while
we're preempted in ret_from_sys_call after checking ti.flags.
Fix it by disabling interrupts before checking
18 matches
Mail list logo