[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGpZZ6un6VT2ZVje0tVXbZkvH_HH+pn2Du6WPa5qeJDOz7rUmg@mail.gmail.com>
Date: Wed, 29 Jul 2020 12:10:17 -0400
From: Andres Beltran <lkmlabelt@...il.com>
To: Stephen Hemminger <sthemmin@...rosoft.com>
Cc: KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Wei Liu <wei.liu@...nel.org>, linux-hyperv@...r.kernel.org,
linux-kernel@...r.kernel.org,
Michael Kelley <mikelley@...rosoft.com>,
Andrea Parri <parri.andrea@...il.com>,
Saruhan Karademir <skarade@...rosoft.com>
Subject: Re: [PATCH] hv_utils: Add validation for untrusted Hyper-V values
On Tue, Jul 28, 2020 at 5:04 PM Stephen Hemminger
<sthemmin@...rosoft.com> wrote:
>
> You may want to use one of the macros that prints this once only.
> This is a "should never happen" type error, so if something goes wrong it might happens so much that journal/syslog would get overloaded.
Certainly, printing error messages once would be ideal if we were only
dealing with Linux kernel bugs. But under the assumption that Hyper-V
can send bogus values at any time, I think it would be better to print
error messages every time so that we are aware of malicious/erroneous
data sent by the host.
Powered by blists - more mailing lists