On Mon, Nov 5, 2018 at 5:15 AM Martin Schwidefsky
wrote:
>
> This patch would work for me:
Thanks, applied,
Linus
On Mon, 5 Nov 2018 14:15:35 +0100
Martin Schwidefsky wrote:
>
> Follow-up question: the __no_sanitize_address_or_inline define has the
> 'notrace'
> option that is missing for __no_kasan_or_inline. We need that option for
> __load_psw_mask, if we do the replacement all users of
On Mon, 5 Nov 2018 07:02:56 +0100
Martin Schwidefsky wrote:
> On Fri, 2 Nov 2018 09:09:32 -0700
> Linus Torvalds wrote:
>
> > On Fri, Nov 2, 2018 at 2:43 AM Andrey Ryabinin
> > wrote:
> > >
> > > You're right, version checks shouldn't matter here. But
> > > __no_sanitize_address_or_inline
On Fri, 2 Nov 2018 09:09:32 -0700
Linus Torvalds wrote:
> On Fri, Nov 2, 2018 at 2:43 AM Andrey Ryabinin
> wrote:
> >
> > You're right, version checks shouldn't matter here. But
> > __no_sanitize_address_or_inline
> > shouldn't have been added in the first place, because we already have
> >
On 11/02/2018 07:11 PM, Linus Torvalds wrote:
> On Fri, Nov 2, 2018 at 6:16 AM Andrey Ryabinin
> wrote:
>>
>> On 11/02/2018 04:46 AM, Linus Torvalds wrote:
>>>
>>> So I _think_ the KASAN config should have a
>>>
>>> depends on CC_IS_GCC && GCC_VERSION >= 40902
>>>
>>> on it, but maybe
On Fri, Nov 2, 2018 at 6:16 AM Andrey Ryabinin wrote:
>
> On 11/02/2018 04:46 AM, Linus Torvalds wrote:
> >
> > So I _think_ the KASAN config should have a
> >
> > depends on CC_IS_GCC && GCC_VERSION >= 40902
> >
> > on it, but maybe there is something I'm missing.
>
> I'd rather use
On Fri, Nov 2, 2018 at 2:43 AM Andrey Ryabinin wrote:
>
> You're right, version checks shouldn't matter here. But
> __no_sanitize_address_or_inline
> shouldn't have been added in the first place, because we already have almost
> the same
>__no_kasan_or_inline:
Ahh, very good.
Vasily, Martin -
On 11/02/2018 04:46 AM, Linus Torvalds wrote:
> On Thu, Nov 1, 2018 at 10:06 AM Linus Torvalds
> wrote:
>>
>> The logic for using __no_sanitize_address *used* to be
>>
>> #if GCC_VERSION >= 40902
>
> Ok, looking around, I think this has less to do with the attribute
> being recognized,
On Fri, Nov 2, 2018 at 2:52 AM Linus Torvalds
wrote:
>
> Anyway, I decided to do the merge by just getting rid of the
> GCC_VERSION check around __no_sanitize_address_or_inline entirely. If
> you enable KASAN, then a function with that marking just won't be
> marked inline.
I was a bit confused
On 11/01/2018 08:06 PM, Linus Torvalds wrote:
> On Mon, Oct 22, 2018 at 3:59 AM Miguel Ojeda
> wrote:
>>
>> Here it is the Compiler Attributes series/tree, which tries to disentangle
>> the include/linux/compiler*.h headers and bring them up to date.
>
> I've finally emptied the "normal" pull
On Thu, Nov 1, 2018 at 10:06 AM Linus Torvalds
wrote:
>
> The logic for using __no_sanitize_address *used* to be
>
> #if GCC_VERSION >= 40902
Ok, looking around, I think this has less to do with the attribute
being recognized, and simply just being because KASAN itself wants
gcc-4.9.2.
I'm
On Thu, Nov 1, 2018 at 6:06 PM Linus Torvalds
wrote:
>
> I'm not sure how much that matters (maybe the original check for 4.9.2
> was just a random pick by Andrey? Added to cc), but together with the
> movement to that looks like it also
> wouldn't want the CONFIG_KASAN tests, I wonder what the
Hi Linus,
Here it is the Compiler Attributes series/tree, which tries to disentangle
the include/linux/compiler*.h headers and bring them up to date.
The patches have been in linux-next for a while, *except* the last two
from Nick which came a bit later. Since AFAIU there will be no linux-next
13 matches
Mail list logo
