lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20191211133302.GD23383@linux.fritz.box> Date: Wed, 11 Dec 2019 14:33:02 +0100 From: Daniel Borkmann <daniel@...earbox.net> To: Toke Høiland-Jørgensen <toke@...hat.com> Cc: Jakub Kicinski <jakub.kicinski@...ronome.com>, Alexei Starovoitov <alexei.starovoitov@...il.com>, lkml <linux-kernel@...r.kernel.org>, netdev@...r.kernel.org, bpf@...r.kernel.org, Martin Lau <kafai@...com> Subject: Re: [PATCH bpf v2] bpftool: Don't crash on missing jited insns or ksyms On Wed, Dec 11, 2019 at 02:20:11PM +0100, Toke Høiland-Jørgensen wrote: > Daniel Borkmann <daniel@...earbox.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/
Powered by blists - more mailing lists