On Fri, Mar 2, 2018 at 2:26 PM, Alexei Starovoitov
wrote:
> On Fri, Mar 02, 2018 at 02:04:17PM -0800, Gianluca Borello wrote:
>> On Fri, Mar 2, 2018 at 12:42 PM, Alexei Starovoitov
>> wrote:
>> >
>> > good catch!
>> > I wonder why sched.h is using this flag insead of relying on #defines from
>>
On Fri, Mar 02, 2018 at 02:04:17PM -0800, Gianluca Borello wrote:
> On Fri, Mar 2, 2018 at 12:42 PM, Alexei Starovoitov
> wrote:
> >
> > good catch!
> > I wonder why sched.h is using this flag insead of relying on #defines from
> > autoconf.h
> > It could have been using CONFIG_HAVE_CC_STACKPROTE
On Fri, Mar 2, 2018 at 2:04 PM, Gianluca Borello wrote:
> On Fri, Mar 2, 2018 at 12:42 PM, Alexei Starovoitov
> wrote:
>>
>> good catch!
>> I wonder why sched.h is using this flag insead of relying on #defines from
>> autoconf.h
>> It could have been using CONFIG_HAVE_CC_STACKPROTECTOR
>> instea
On Fri, Mar 2, 2018 at 12:42 PM, Alexei Starovoitov
wrote:
>
> good catch!
> I wonder why sched.h is using this flag insead of relying on #defines from
> autoconf.h
> It could have been using CONFIG_HAVE_CC_STACKPROTECTOR
> instead of CONFIG_CC_STACKPROTECTOR, no ?
>
Thanks for your reply Alexei
On Fri, Mar 02, 2018 at 12:09:57PM -0800, Gianluca Borello wrote:
> Hello,
>
> While testing bpf-next, I noticed that I was reading garbage when
> accessing some task_struct members, and the issue seems caused by the
> recent commit 2bc2f688fdf8 ("Makefile: move stack-protector
> availability out
Hello,
While testing bpf-next, I noticed that I was reading garbage when
accessing some task_struct members, and the issue seems caused by the
recent commit 2bc2f688fdf8 ("Makefile: move stack-protector
availability out of Kconfig") which removes CONFIG_CC_STACKPROTECTOR
from autoconf.h.
When I c
