From: Wang YanQing <udknight@gmail.com>
To: stable@vger.kernel.org
Cc: stephen@networkplumber.org, ast@kernel.org,
songliubraving@fb.com, yhs@fb.com, daniel@iogearbox.net,
itugrok@yahoo.com, bpf@vger.kernel.org
Subject: [PATCH] bpf, x32: Fix bug with ALU64 {LSH, RSH, ARSH} BPF_X shift by 0
Date: Thu, 21 Nov 2019 15:45:11 +0800 [thread overview]
Message-ID: <20191121074511.GC15326@udknight> (raw)
commit 68a8357ec15bdce55266e9fba8b8b3b8143fa7d2 upstream.
The fix only affects x32 bpf jit, and it is critical to use x32 bpf jit on a
unpatched system, so I think we should backport it to the only affected stable
kernel version: v4.19
Thanks.
Cc: <stable@vger.kernel.org> #4.19
Signed-off-by: Wang YanQing <udknight@gmail.com>
reply other threads:[~2019-11-21 7:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20191121074511.GC15326@udknight \
--to=udknight@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=itugrok@yahoo.com \
--cc=songliubraving@fb.com \
--cc=stable@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=yhs@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 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).