From: Wang YanQing <udknight@gmail.com>
To: stable@vger.kernel.org
Subject: [PATCH] bpf, x32: Fix bug with ALU64 {LSH, RSH, ARSH} BPF_K shift by 0
Date: Thu, 21 Nov 2019 15:45:29 +0800 [thread overview]
Message-ID: <20191121074529.GD15326@udknight> (raw)
commit 6fa632e719eec4d1b1ebf3ddc0b2d667997b057b 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>
next reply other threads:[~2019-11-21 7:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 7:45 Wang YanQing [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-21 7:47 [PATCH] bpf, x32: Fix bug with ALU64 {LSH, RSH, ARSH} BPF_K shift by 0 Wang YanQing
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=20191121074529.GD15326@udknight \
--to=udknight@gmail.com \
--cc=stable@vger.kernel.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 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.