From: Edward Liaw <edliaw@google.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"David S. Miller" <davem@davemloft.net>,
bpf@vger.kernel.org, kernel-team <kernel-team@android.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
John Fastabend <john.fastabend@gmail.com>,
Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
Subject: Re: [PATCH 4.14 v2 1/4] bpf: Do not use ax register in interpreter on div/mod
Date: Thu, 23 Feb 2023 13:29:42 -0800 [thread overview]
Message-ID: <CAG4es9WoVhTEGLmokfXA8YaJC+nWBOicFKpuePbidtm9cd0c2g@mail.gmail.com> (raw)
In-Reply-To: <Y/fICk4NYFEF9EoS@kroah.com>
> On Thu, Feb 23, 2023 at 10:46:50AM -0800, Edward Liaw wrote:
> > > What is the git commit id in Linus's tree of this commit?
> >
> > Hi Greg,
> > It is a partial revert of 144cd91c4c2bced6eb8a7e25e590f6618a11e854.
>
> Please document that in the changelog text very very well when you
> resend this.
Sorry, I made a mistake. The original commit was made to 4.19.y with
commit id c348d806ed1d3075af52345344243824d72c4945.
next prev parent reply other threads:[~2023-02-23 21:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 19:29 [PATCH 4.14 v2 0/4] BPF fixes for CVE-2021-3444 and CVE-2021-3600 Edward Liaw
2023-02-22 19:29 ` [PATCH 4.14 v2 1/4] bpf: Do not use ax register in interpreter on div/mod Edward Liaw
2023-02-23 9:01 ` Greg KH
2023-02-23 18:46 ` Edward Liaw
2023-02-23 20:09 ` Greg KH
2023-02-23 21:29 ` Edward Liaw [this message]
2023-02-22 19:29 ` [PATCH 4.14 v2 2/4] bpf: fix subprog verifier bypass by div/mod by 0 exception Edward Liaw
2023-02-22 19:29 ` [PATCH 4.14 v2 3/4] bpf: Fix 32 bit src register truncation on div/mod Edward Liaw
2023-02-22 19:29 ` [PATCH 4.14 v2 4/4] bpf: Fix truncation handling for mod32 dst reg wrt zero Edward Liaw
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=CAG4es9WoVhTEGLmokfXA8YaJC+nWBOicFKpuePbidtm9cd0c2g@mail.gmail.com \
--to=edliaw@google.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cascardo@canonical.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=john.fastabend@gmail.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 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).