Re: [PATCH v2 1/7] sysfs/cpu: Add "Unknown" vulnerability state

2019-01-04 Thread Will Deacon
On Fri, Jan 04, 2019 at 03:18:05PM +0100, Greg Kroah-Hartman wrote: > On Fri, Jan 04, 2019 at 02:08:32PM +, Dave Martin wrote: > > On Thu, Jan 03, 2019 at 05:48:31PM +0100, Greg Kroah-Hartman wrote: > > > On Thu, Jan 03, 2019 at 10:38:16AM -0600, Jeremy Linton wrote: > > > > On 01/03/2019 03:38

Re: [PATCH v2 1/7] sysfs/cpu: Add "Unknown" vulnerability state

2019-01-04 Thread Greg Kroah-Hartman
On Fri, Jan 04, 2019 at 02:08:32PM +, Dave Martin wrote: > On Thu, Jan 03, 2019 at 05:48:31PM +0100, Greg Kroah-Hartman wrote: > > On Thu, Jan 03, 2019 at 10:38:16AM -0600, Jeremy Linton wrote: > > > On 01/03/2019 03:38 AM, Greg Kroah-Hartman wrote: > > > > On Wed, Jan 02, 2019 at 06:49:15PM -0

Re: [PATCH v2 1/7] sysfs/cpu: Add "Unknown" vulnerability state

2019-01-04 Thread Dave Martin
On Thu, Jan 03, 2019 at 05:48:31PM +0100, Greg Kroah-Hartman wrote: > On Thu, Jan 03, 2019 at 10:38:16AM -0600, Jeremy Linton wrote: > > On 01/03/2019 03:38 AM, Greg Kroah-Hartman wrote: > > > On Wed, Jan 02, 2019 at 06:49:15PM -0600, Jeremy Linton wrote: > > > > There is a lot of variation in the

Re: [PATCH v2 1/7] sysfs/cpu: Add "Unknown" vulnerability state

2019-01-04 Thread Will Deacon
On Thu, Jan 03, 2019 at 02:32:44PM -0600, Jeremy Linton wrote: > On 01/03/2019 01:30 PM, Stefan Wahren wrote: > > > Jeremy Linton hat am 3. Januar 2019 um 17:46 > > > geschrieben: > > > On 01/03/2019 10:37 AM, Dave Martin wrote: > > > > On Wed, Jan 02, 2019 at 06:49:15PM -0600, Jeremy Linton wrot

Re: [PATCH v2 1/7] sysfs/cpu: Add "Unknown" vulnerability state

2019-01-03 Thread Jeremy Linton
Hi, On 01/03/2019 01:30 PM, Stefan Wahren wrote: Hi Jeremy, Jeremy Linton hat am 3. Januar 2019 um 17:46 geschrieben: Hi, On 01/03/2019 10:37 AM, Dave Martin wrote: On Wed, Jan 02, 2019 at 06:49:15PM -0600, Jeremy Linton wrote: There is a lot of variation in the Arm ecosystem. Because o

Re: [PATCH v2 1/7] sysfs/cpu: Add "Unknown" vulnerability state

2019-01-03 Thread Stefan Wahren
Hi Jeremy, > Jeremy Linton hat am 3. Januar 2019 um 17:46 > geschrieben: > > > Hi, > > On 01/03/2019 10:37 AM, Dave Martin wrote: > > On Wed, Jan 02, 2019 at 06:49:15PM -0600, Jeremy Linton wrote: > >> There is a lot of variation in the Arm ecosystem. Because of this, > >> there exist possibl

Re: [PATCH v2 1/7] sysfs/cpu: Add "Unknown" vulnerability state

2019-01-03 Thread Greg Kroah-Hartman
On Thu, Jan 03, 2019 at 10:38:16AM -0600, Jeremy Linton wrote: > On 01/03/2019 03:38 AM, Greg Kroah-Hartman wrote: > > On Wed, Jan 02, 2019 at 06:49:15PM -0600, Jeremy Linton wrote: > > > There is a lot of variation in the Arm ecosystem. Because of this, > > > there exist possible cases where the k

Re: [PATCH v2 1/7] sysfs/cpu: Add "Unknown" vulnerability state

2019-01-03 Thread Jeremy Linton
Hi, On 01/03/2019 10:37 AM, Dave Martin wrote: On Wed, Jan 02, 2019 at 06:49:15PM -0600, Jeremy Linton wrote: There is a lot of variation in the Arm ecosystem. Because of this, there exist possible cases where the kernel cannot authoritatively determine if a machine is vulnerable. Rather than

Re: [PATCH v2 1/7] sysfs/cpu: Add "Unknown" vulnerability state

2019-01-03 Thread Jeremy Linton
On 01/03/2019 03:38 AM, Greg Kroah-Hartman wrote: On Wed, Jan 02, 2019 at 06:49:15PM -0600, Jeremy Linton wrote: There is a lot of variation in the Arm ecosystem. Because of this, there exist possible cases where the kernel cannot authoritatively determine if a machine is vulnerable. Really?

Re: [PATCH v2 1/7] sysfs/cpu: Add "Unknown" vulnerability state

2019-01-03 Thread Dave Martin
On Wed, Jan 02, 2019 at 06:49:15PM -0600, Jeremy Linton wrote: > There is a lot of variation in the Arm ecosystem. Because of this, > there exist possible cases where the kernel cannot authoritatively > determine if a machine is vulnerable. > > Rather than guess the vulnerability status in cases w

Re: [PATCH v2 1/7] sysfs/cpu: Add "Unknown" vulnerability state

2019-01-03 Thread Greg Kroah-Hartman
On Wed, Jan 02, 2019 at 06:49:15PM -0600, Jeremy Linton wrote: > There is a lot of variation in the Arm ecosystem. Because of this, > there exist possible cases where the kernel cannot authoritatively > determine if a machine is vulnerable. Really? Why not? What keeps you from "knowing" this? C

[PATCH v2 1/7] sysfs/cpu: Add "Unknown" vulnerability state

2019-01-02 Thread Jeremy Linton
There is a lot of variation in the Arm ecosystem. Because of this, there exist possible cases where the kernel cannot authoritatively determine if a machine is vulnerable. Rather than guess the vulnerability status in cases where the mitigation is disabled or the firmware isn't responding correctl