Hi Dima,
[auto build test WARNING on v4.12]
[cannot apply to cgroup/for-next linus/master v4.13-rc2 v4.13-rc1 next-20170728]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Dima,
[auto build test WARNING on v4.12]
[cannot apply to cgroup/for-next linus/master v4.13-rc2 v4.13-rc1 next-20170728]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Fri, Jul 28, 2017 at 7:05 AM, Vlastimil Babka wrote:
> On 07/28/2017 11:30 AM, Peter Zijlstra wrote:
>> On Fri, Jul 28, 2017 at 09:45:16AM +0200, Vlastimil Babka wrote:
>>> [+CC PeterZ]
>>>
>>> On 07/27/2017 06:46 PM, Dima Zavin wrote:
In codepaths that use the begin/retry
On Fri, Jul 28, 2017 at 7:05 AM, Vlastimil Babka wrote:
> On 07/28/2017 11:30 AM, Peter Zijlstra wrote:
>> On Fri, Jul 28, 2017 at 09:45:16AM +0200, Vlastimil Babka wrote:
>>> [+CC PeterZ]
>>>
>>> On 07/27/2017 06:46 PM, Dima Zavin wrote:
In codepaths that use the begin/retry interface for
On 07/28/2017 11:30 AM, Peter Zijlstra wrote:
> On Fri, Jul 28, 2017 at 09:45:16AM +0200, Vlastimil Babka wrote:
>> [+CC PeterZ]
>>
>> On 07/27/2017 06:46 PM, Dima Zavin wrote:
>>> In codepaths that use the begin/retry interface for reading
>>> mems_allowed_seq with irqs disabled, there exists a
On 07/28/2017 11:30 AM, Peter Zijlstra wrote:
> On Fri, Jul 28, 2017 at 09:45:16AM +0200, Vlastimil Babka wrote:
>> [+CC PeterZ]
>>
>> On 07/27/2017 06:46 PM, Dima Zavin wrote:
>>> In codepaths that use the begin/retry interface for reading
>>> mems_allowed_seq with irqs disabled, there exists a
On Fri, Jul 28, 2017 at 09:45:16AM +0200, Vlastimil Babka wrote:
> [+CC PeterZ]
>
> On 07/27/2017 06:46 PM, Dima Zavin wrote:
> > In codepaths that use the begin/retry interface for reading
> > mems_allowed_seq with irqs disabled, there exists a race condition that
> > stalls the patch process
On Fri, Jul 28, 2017 at 09:45:16AM +0200, Vlastimil Babka wrote:
> [+CC PeterZ]
>
> On 07/27/2017 06:46 PM, Dima Zavin wrote:
> > In codepaths that use the begin/retry interface for reading
> > mems_allowed_seq with irqs disabled, there exists a race condition that
> > stalls the patch process
On Fri, Jul 28, 2017 at 12:45 AM, Vlastimil Babka wrote:
> [+CC PeterZ]
>
> On 07/27/2017 06:46 PM, Dima Zavin wrote:
>> In codepaths that use the begin/retry interface for reading
>> mems_allowed_seq with irqs disabled, there exists a race condition that
>> stalls the patch
On Fri, Jul 28, 2017 at 12:45 AM, Vlastimil Babka wrote:
> [+CC PeterZ]
>
> On 07/27/2017 06:46 PM, Dima Zavin wrote:
>> In codepaths that use the begin/retry interface for reading
>> mems_allowed_seq with irqs disabled, there exists a race condition that
>> stalls the patch process after only
[+CC PeterZ]
On 07/27/2017 06:46 PM, Dima Zavin wrote:
> In codepaths that use the begin/retry interface for reading
> mems_allowed_seq with irqs disabled, there exists a race condition that
> stalls the patch process after only modifying a subset of the
> static_branch call sites.
>
> This
[+CC PeterZ]
On 07/27/2017 06:46 PM, Dima Zavin wrote:
> In codepaths that use the begin/retry interface for reading
> mems_allowed_seq with irqs disabled, there exists a race condition that
> stalls the patch process after only modifying a subset of the
> static_branch call sites.
>
> This
On Thu, Jul 27, 2017 at 12:51 PM, Andrew Morton
wrote:
> On Thu, 27 Jul 2017 09:46:08 -0700 Dima Zavin wrote:
>
>> - Applied on top of v4.12 since one of the callers in page_alloc.c changed.
>>Still only tested on v4.9.36 and compile tested
On Thu, Jul 27, 2017 at 12:51 PM, Andrew Morton
wrote:
> On Thu, 27 Jul 2017 09:46:08 -0700 Dima Zavin wrote:
>
>> - Applied on top of v4.12 since one of the callers in page_alloc.c changed.
>>Still only tested on v4.9.36 and compile tested against v4.12.
>
> That's a problem - this doesn't
On Thu, Jul 27, 2017 at 12:48 PM, Andrew Morton
wrote:
> On Thu, 27 Jul 2017 09:46:08 -0700 Dima Zavin wrote:
>
>> In codepaths that use the begin/retry interface for reading
>> mems_allowed_seq with irqs disabled, there exists a race condition that
On Thu, Jul 27, 2017 at 12:48 PM, Andrew Morton
wrote:
> On Thu, 27 Jul 2017 09:46:08 -0700 Dima Zavin wrote:
>
>> In codepaths that use the begin/retry interface for reading
>> mems_allowed_seq with irqs disabled, there exists a race condition that
>> stalls the patch process after only
On Thu, 27 Jul 2017 09:46:08 -0700 Dima Zavin wrote:
> - Applied on top of v4.12 since one of the callers in page_alloc.c changed.
>Still only tested on v4.9.36 and compile tested against v4.12.
That's a problem - this doesn't come close to applying on current
mainline.
On Thu, 27 Jul 2017 09:46:08 -0700 Dima Zavin wrote:
> - Applied on top of v4.12 since one of the callers in page_alloc.c changed.
>Still only tested on v4.9.36 and compile tested against v4.12.
That's a problem - this doesn't come close to applying on current
mainline. I can fix that I
On Thu, 27 Jul 2017 09:46:08 -0700 Dima Zavin wrote:
> In codepaths that use the begin/retry interface for reading
> mems_allowed_seq with irqs disabled, there exists a race condition that
> stalls the patch process after only modifying a subset of the
> static_branch call
On Thu, 27 Jul 2017 09:46:08 -0700 Dima Zavin wrote:
> In codepaths that use the begin/retry interface for reading
> mems_allowed_seq with irqs disabled, there exists a race condition that
> stalls the patch process after only modifying a subset of the
> static_branch call sites.
>
> This
In codepaths that use the begin/retry interface for reading
mems_allowed_seq with irqs disabled, there exists a race condition that
stalls the patch process after only modifying a subset of the
static_branch call sites.
This problem manifested itself as a dead lock in the slub
allocator, inside
In codepaths that use the begin/retry interface for reading
mems_allowed_seq with irqs disabled, there exists a race condition that
stalls the patch process after only modifying a subset of the
static_branch call sites.
This problem manifested itself as a dead lock in the slub
allocator, inside
22 matches
Mail list logo