From: Daniel Borkmann <daniel@iogearbox.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alexei Starovoitov <ast@kernel.org>,
psodagud@codeaurora.org,
Network Development <netdev@vger.kernel.org>,
Chenbo Feng <fengc@google.com>,
Richard Smith <richard-llvm@metafoo.co.uk>,
Chandler Carruth <chandlerc@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kbuild: disable clang's default use of -fmerge-all-constants
Date: Wed, 21 Mar 2018 01:38:45 +0100 [thread overview]
Message-ID: <bd7b0d23-519e-ca8b-a768-1440a4bc90d3@iogearbox.net> (raw)
In-Reply-To: <CA+55aFw94wSeOvs1JO2iPHXgpwWQ-EF6v0XYwjFrQN1wr5tY-A@mail.gmail.com>
On 03/21/2018 01:36 AM, Linus Torvalds wrote:
> On Tue, Mar 20, 2018 at 5:18 PM, Daniel Borkmann <daniel@iogearbox.net> wrote:
>> Prasad reported that he has seen crashes in BPF subsystem with netd
>> on Android with arm64 in the form of (note, the taint is unrelated):
>
> Ack. This looks good to me. And thanks for noticing the behavior wrt
> the correct gcc merging.
>
>> [ Hi Linus, feel free to take this fix directly if you want.
>> Alternatively, we could route it via bpf tree. Thanks a
>> lot for your feedback! ]
>
> So since it's your patch and the only known issue comes from the bpf
> side, I think it should just go through the bpf tree, and I expect it
> to get to me through all the usual channels.
Yeah, that's fine, thanks for letting us know!
Best,
Daniel
next prev parent reply other threads:[~2018-03-21 0:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 0:18 Daniel Borkmann
2018-03-21 0:36 ` Linus Torvalds
2018-03-21 0:38 ` Daniel Borkmann [this message]
2018-03-21 0:58 ` Alexei Starovoitov
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=bd7b0d23-519e-ca8b-a768-1440a4bc90d3@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=chandlerc@gmail.com \
--cc=fengc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=psodagud@codeaurora.org \
--cc=richard-llvm@metafoo.co.uk \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®