From: Daniel Borkmann <daniel@iogearbox.net>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: Jakub Kicinski <jakub.kicinski@netronome.com>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
Martin Lau <kafai@fb.com>
Subject: Re: [PATCH bpf v2] bpftool: Don't crash on missing jited insns or ksyms
Date: Wed, 11 Dec 2019 14:33:02 +0100 [thread overview]
Message-ID: <20191211133302.GD23383@linux.fritz.box> (raw)
In-Reply-To: <87zhfzf184.fsf@toke.dk>
On Wed, Dec 11, 2019 at 02:20:11PM +0100, Toke Høiland-Jørgensen wrote:
> Daniel Borkmann <daniel@iogearbox.net> writes:
> > On Tue, Dec 10, 2019 at 10:09:55PM +0100, Toke Høiland-Jørgensen wrote:
> > [...]
> >> Anyhow, I don't suppose it'll hurt to have the Fixes: tag(s) in there;
> >> does Patchwork pick these up (or can you guys do that when you apply
> >> this?), or should I resend?
> >
> > Fixes tags should /always/ be present if possible, since they help to provide
> > more context even if the buggy commit was in bpf-next, for example.
>
> ACK, will do. Thank you for picking them up for this patch (did you do
> that manually, or is this part of your scripts?)
Manually right now, but if you have some cycles, happy to pick up a patch [0]. :)
[0] https://git.kernel.org/pub/scm/linux/kernel/git/dborkman/pw.git/
next prev parent reply other threads:[~2019-12-11 13:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 18:14 [PATCH bpf v2] bpftool: Don't crash on missing jited insns or ksyms Toke Høiland-Jørgensen
2019-12-10 18:21 ` Martin Lau
2019-12-10 20:54 ` Jakub Kicinski
2019-12-10 21:09 ` Toke Høiland-Jørgensen
2019-12-10 21:24 ` Jakub Kicinski
2019-12-10 21:31 ` Alexei Starovoitov
2019-12-10 21:52 ` Jakub Kicinski
2019-12-10 22:53 ` Alexei Starovoitov
2019-12-11 13:08 ` Daniel Borkmann
2019-12-11 13:20 ` Toke Høiland-Jørgensen
2019-12-11 13:33 ` Daniel Borkmann [this message]
2019-12-11 13:01 ` Daniel Borkmann
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=20191211133302.GD23383@linux.fritz.box \
--to=daniel@iogearbox.net \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=jakub.kicinski@netronome.com \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=toke@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.