Re: [PATCH v3] cpuset: fix a deadlock due to incomplete patching of cpusets_enabled()

2017-07-31 Thread Dima Zavin
On Mon, Jul 31, 2017 at 1:02 AM, Vlastimil Babka wrote: > On 07/31/2017 06:01 AM, 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

Re: [PATCH v3] cpuset: fix a deadlock due to incomplete patching of cpusets_enabled()

2017-07-31 Thread Vlastimil Babka
On 07/31/2017 06:01 AM, 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 problem manifested

Re: [PATCH v3] cpuset: fix a deadlock due to incomplete patching of cpusets_enabled()

2017-07-30 Thread Dima Zavin
On Sun, Jul 30, 2017 at 9:01 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 problem ma

[PATCH v3] cpuset: fix a deadlock due to incomplete patching of cpusets_enabled()

2017-07-30 Thread Dima Zavin
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 ge