Re: [PATCH v2] sched: unlikely corrupted stack end

* WANG Chao wrote: > > > 在 2016年6月14日，下午6:26，Ingo Molnar 写道： > > > > > > * WANG Chao wrote: > > > >> > >>> 在 2016年6月14日，下午4:56，Ingo Molnar 写道： > >>> > >>> > >>> * WANG Chao wrote: > >>> > unlikely() was dropped in commit ce03e4137bb2 ("sched/core: Drop > unlikely behind BUG

Re: [PATCH v2] sched: unlikely corrupted stack end

> 在 2016年6月14日，下午6:26，Ingo Molnar 写道： > > > * WANG Chao wrote: > >> >>> 在 2016年6月14日，下午4:56，Ingo Molnar 写道： >>> >>> >>> * WANG Chao wrote: >>> unlikely() was dropped in commit ce03e4137bb2 ("sched/core: Drop unlikely behind BUG_ON()"), but commit 29d6455178a0 ("sched: panic on

Re: [PATCH v2] sched: unlikely corrupted stack end

* WANG Chao wrote: > > > 在 2016年6月14日，下午4:56，Ingo Molnar 写道： > > > > > > * WANG Chao wrote: > > > >> unlikely() was dropped in commit ce03e4137bb2 ("sched/core: Drop > >> unlikely behind BUG_ON()"), but commit 29d6455178a0 ("sched: panic on > >> corrupted stack end") dropped BUG_ON() and c

Re: [PATCH v2] sched: unlikely corrupted stack end

> 在 2016年6月14日，下午4:56，Ingo Molnar 写道： > > > * WANG Chao wrote: > >> unlikely() was dropped in commit ce03e4137bb2 ("sched/core: Drop >> unlikely behind BUG_ON()"), but commit 29d6455178a0 ("sched: panic on >> corrupted stack end") dropped BUG_ON() and called panic directly. >> >> Now we shou

Re: [PATCH v2] sched: unlikely corrupted stack end

Hi, [auto build test ERROR on tip/sched/core] [also build test ERROR on v4.7-rc3 next-20160614] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/WANG-Chao/sched-unlikely-corrupted-stack-end/201606

Re: [PATCH v2] sched: unlikely corrupted stack end

* WANG Chao wrote: > unlikely() was dropped in commit ce03e4137bb2 ("sched/core: Drop > unlikely behind BUG_ON()"), but commit 29d6455178a0 ("sched: panic on > corrupted stack end") dropped BUG_ON() and called panic directly. > > Now we should bring unlikely() back for branch prediction. While