From: Greg KH <gregkh@linuxfoundation•org>
To: Dan Williams <dan.j.williams@intel•com>
Cc: linux-kernel@vger•kernel.org, linux-arch@vger•kernel.org,
akpm@linux-foundation•org, kernel-hardening@lists•openwall.com,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6•org>,
netdev@vger•kernel.org, Alexey Kuznetsov <kuznet@ms2•inr.ac.ru>,
tglx@linutronix•de, torvalds@linux-foundation•org,
"David S. Miller" <davem@davemloft•net>,
Elena Reshetova <elena.reshetova@intel•com>,
alan@linux•intel.com
Subject: Re: [PATCH v2 10/19] ipv4: prevent bounds-check bypass via speculative execution
Date: Fri, 12 Jan 2018 08:59:07 +0100 [thread overview]
Message-ID: <20180112075907.GA3391@kroah.com> (raw)
In-Reply-To: <151571803884.27429.7578279171286065970.stgit@dwillia2-desk3.amr.corp.intel.com>
On Thu, Jan 11, 2018 at 04:47:18PM -0800, Dan Williams wrote:
> Static analysis reports that 'offset' may be a user controlled value
> that is used as a data dependency reading from a raw_frag_vec buffer.
> In order to avoid potential leaks of kernel memory values, block
> speculative execution of the instruction stream that could issue further
> reads based on an invalid '*(rfv->c + offset)' value.
>
> Based on an original patch by Elena Reshetova.
There is the "Co-Developed-by:" tag now, if you want to use it...
> Cc: "David S. Miller" <davem@davemloft•net>
> Cc: Alexey Kuznetsov <kuznet@ms2•inr.ac.ru>
> Cc: Hideaki YOSHIFUJI <yoshfuji@linux-ipv6•org>
> Cc: netdev@vger•kernel.org
> Signed-off-by: Elena Reshetova <elena.reshetova@intel•com>
> Signed-off-by: Dan Williams <dan.j.williams@intel•com>
> ---
> net/ipv4/raw.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
Ugh, what is this, the 4th time I've said "I don't think this is an
issue, so why are you changing this code." to this patch. To be
followed by a "oh yeah, you are right, I'll drop it", only to see it
show back up in the next time this patch series is sent out?
Same for the other patches in this series that I have reviewed 4, maybe
5, times already. The "v2" is not very true here...
thanks,
greg k-h
next prev parent reply other threads:[~2018-01-12 7:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 0:46 [PATCH v2 00/19] prevent bounds-check bypass via speculative execution Dan Williams
2018-01-12 0:47 ` [PATCH v2 09/19] ipv6: " Dan Williams
2018-01-12 0:47 ` [PATCH v2 10/19] ipv4: " Dan Williams
2018-01-12 7:59 ` Greg KH [this message]
2018-01-12 18:47 ` Dan Williams
2018-01-13 8:56 ` Greg KH
2018-01-12 0:47 ` [PATCH v2 15/19] carl9170: " Dan Williams
2018-01-12 14:42 ` Christian Lamparter
2018-01-12 18:39 ` Dan Williams
2018-01-12 20:01 ` Christian Lamparter
2018-01-12 23:05 ` Dan Williams
2018-01-12 0:47 ` [PATCH v2 16/19] p54: " Dan Williams
2018-01-12 0:48 ` [PATCH v2 18/19] cw1200: " Dan Williams
2018-01-12 0:48 ` [PATCH v2 19/19] net: mpls: " Dan Williams
2018-01-12 1:19 ` [PATCH v2 00/19] " Linus Torvalds
2018-01-12 1:41 ` Dan Williams
2018-01-18 13:18 ` Will Deacon
2018-01-18 16:58 ` Dan Williams
2018-01-18 17:05 ` Will Deacon
2018-01-18 21:41 ` Laurent Pinchart
2018-01-13 0:15 ` Tony Luck
2018-01-13 18:51 ` Linus Torvalds
2018-01-16 19:21 ` Tony Luck
2018-01-12 10:02 ` Russell King - ARM Linux
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=20180112075907.GA3391@kroah.com \
--to=gregkh@linuxfoundation$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=alan@linux$(echo .)intel.com \
--cc=dan.j.williams@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=elena.reshetova@intel$(echo .)com \
--cc=kernel-hardening@lists$(echo .)openwall.com \
--cc=kuznet@ms2$(echo .)inr.ac.ru \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=tglx@linutronix$(echo .)de \
--cc=torvalds@linux-foundation$(echo .)org \
--cc=yoshfuji@linux-ipv6$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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