From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alexei Starovoitov <ast@kernel.org>
Cc: Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>
Cc: stable <stable@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] bpf: explicitly memset the bpf_attr structure
Date: Fri, 20 Mar 2020 17:59:46 +0000 [thread overview]
Message-ID: <20200320175947.AB1B920777@mail.kernel.org> (raw)
In-Reply-To: <20200320094813.GA421650@kroah.com>
Hi
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.5.10, v5.4.26, v4.19.111, v4.14.173, v4.9.216, v4.4.216.
v5.5.10: Build OK!
v5.4.26: Build OK!
v4.19.111: Build OK!
v4.14.173: Build OK!
v4.9.216: Failed to apply! Possible dependencies:
Unable to calculate
v4.4.216: Failed to apply! Possible dependencies:
Unable to calculate
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-03-20 17:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 9:48 [PATCH] bpf: explicitly memset the bpf_attr structure Greg Kroah-Hartman
2020-03-20 15:23 ` Yonghong Song
2020-03-20 15:46 ` Greg Kroah-Hartman
2020-03-20 15:24 ` Daniel Borkmann
2020-03-20 15:31 ` Yonghong Song
2020-03-20 15:45 ` Greg Kroah-Hartman
2020-03-20 16:04 ` Daniel Borkmann
2020-03-20 16:15 ` Greg Kroah-Hartman
2020-03-20 16:22 ` [PATCH] bpf: explicitly memset some bpf info structures declared on the stack Greg Kroah-Hartman
2020-03-20 18:34 ` Yonghong Song
2020-03-20 20:07 ` Daniel Borkmann
2020-03-20 17:59 ` Sasha Levin [this message]
2020-03-20 20:07 ` [PATCH] bpf: explicitly memset the bpf_attr structure 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=20200320175947.AB1B920777@mail.kernel.org \
--to=sashal@kernel.org \
--cc=kafai@fb.com \
--cc=songliubraving@fb.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.