linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Paul Semel <semelpaul@gmail.com>
Cc: linux-kernel@vger.kernel.org, andreyknvl@google.com,
	vincenzo.frascino@arm.com, catalin.marinas@arm.com,
	linux-arm-kernel@lists.infradead.org, paul.semel@datadoghq.com
Subject: Re: [PATCH] arm64: kasan: fix include error in MTE functions
Date: Wed, 9 Mar 2022 11:39:35 +0000	[thread overview]
Message-ID: <20220309113935.GA352@willie-the-truck> (raw)
In-Reply-To: <bacb5387-2992-97e4-0c48-1ed925905bee@gmail.com>

On Tue, Mar 08, 2022 at 10:30:58AM +0100, Paul Semel wrote:
> Fix `error: expected string literal in 'asm'`.
> This happens when compiling an ebpf object file that includes
> `net/net_namespace.h` from linux kernel headers.
> 
> Include trace:
>     include/net/net_namespace.h:10
>     include/linux/workqueue.h:9
>     include/linux/timer.h:8
>     include/linux/debugobjects.h:6
>     include/linux/spinlock.h:90
>     include/linux/workqueue.h:9
>     arch/arm64/include/asm/spinlock.h:9
>     arch/arm64/include/generated/asm/qrwlock.h:1
>     include/asm-generic/qrwlock.h:14
>     arch/arm64/include/asm/processor.h:33
>     arch/arm64/include/asm/kasan.h:9
>     arch/arm64/include/asm/mte-kasan.h:45
>     arch/arm64/include/asm/mte-def.h:14

Do you know where this issue was introduced? I can't tell whether this patch
is a fix for 5.17, or something needed only for 5.18 (and if so, which tree
introduced the problem).

Thanks,

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-03-09 11:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08  9:30 [PATCH] arm64: kasan: fix include error in MTE functions Paul Semel
2022-03-09 11:39 ` Will Deacon [this message]
2022-03-09 12:48   ` Paul Semel
2022-03-09 19:13 ` Catalin Marinas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220309113935.GA352@willie-the-truck \
    --to=will@kernel.org \
    --cc=andreyknvl@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.semel@datadoghq.com \
    --cc=semelpaul@gmail.com \
    --cc=vincenzo.frascino@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).