Re: [PATCH v2 13/19] udf: prevent bounds-check bypass via speculative execution

2018-01-15 Thread Dan Williams
On Mon, Jan 15, 2018 at 2:32 AM, Jan Kara wrote: > On Thu 11-01-18 16:47:35, Dan Williams wrote: >> Static analysis reports that 'eahd->appAttrLocation' and >> 'eahd->impAttrLocation' may be a user controlled values that are used as >> data dependencies for calculating source and

Re: [PATCH v2 13/19] udf: prevent bounds-check bypass via speculative execution

2018-01-15 Thread Dan Williams
On Mon, Jan 15, 2018 at 2:32 AM, Jan Kara wrote: > On Thu 11-01-18 16:47:35, Dan Williams wrote: >> Static analysis reports that 'eahd->appAttrLocation' and >> 'eahd->impAttrLocation' may be a user controlled values that are used as >> data dependencies for calculating source and destination

Re: [PATCH v2 13/19] udf: prevent bounds-check bypass via speculative execution

2018-01-15 Thread Jan Kara
On Thu 11-01-18 16:47:35, Dan Williams wrote: > Static analysis reports that 'eahd->appAttrLocation' and > 'eahd->impAttrLocation' may be a user controlled values that are used as > data dependencies for calculating source and destination buffers for > memmove operations. In order to avoid

Re: [PATCH v2 13/19] udf: prevent bounds-check bypass via speculative execution

2018-01-15 Thread Jan Kara
On Thu 11-01-18 16:47:35, Dan Williams wrote: > Static analysis reports that 'eahd->appAttrLocation' and > 'eahd->impAttrLocation' may be a user controlled values that are used as > data dependencies for calculating source and destination buffers for > memmove operations. In order to avoid

[PATCH v2 13/19] udf: prevent bounds-check bypass via speculative execution

2018-01-11 Thread Dan Williams
Static analysis reports that 'eahd->appAttrLocation' and 'eahd->impAttrLocation' may be a user controlled values that are used as data dependencies for calculating source and destination buffers for memmove operations. In order to avoid potential leaks of kernel memory values, block speculative

[PATCH v2 13/19] udf: prevent bounds-check bypass via speculative execution

2018-01-11 Thread Dan Williams
Static analysis reports that 'eahd->appAttrLocation' and 'eahd->impAttrLocation' may be a user controlled values that are used as data dependencies for calculating source and destination buffers for memmove operations. In order to avoid potential leaks of kernel memory values, block speculative