RE: [PATCH v2] i40e/i40evf: fix out-of-bounds read of cpumask

ists.osuosl.org>; > netdev@vger.kernel.org; > sta...@vger.kernel.org; Juergen Gross <jgr...@suse.com> > Subject: Re: [PATCH v2] i40e/i40evf: fix out-of-bounds read of cpumask > > [Fixed Cc: address for stable, Cc'ed Juergen] > > On Tue, 22 Aug 2017 14:04:42 -0700 >

Re: [PATCH v2] i40e/i40evf: fix out-of-bounds read of cpumask

[Fixed Cc: address for stable, Cc'ed Juergen] On Tue, 22 Aug 2017 14:04:42 -0700 Jacob Keller wrote: > When responding to an affinity hint we directly copied a cpumask value, > intsead of using cpumask_copy. According to cpumask.h this is not > correct because

RE: [PATCH v2] i40e/i40evf: fix out-of-bounds read of cpumask

er, Jacob E <jacob.e.kel...@intel.com>; > sta...@vger.kernel.org#4.10+ > Subject: [PATCH v2] i40e/i40evf: fix out-of-bounds read of cpumask > > When responding to an affinity hint we directly copied a cpumask value, > intsead of using cpumask_copy. According to cpumask.h this is not &

[PATCH v2] i40e/i40evf: fix out-of-bounds read of cpumask

When responding to an affinity hint we directly copied a cpumask value, intsead of using cpumask_copy. According to cpumask.h this is not correct because cpumask_t is only guaranteed to have enough space for the number of CPUs in the system, and may not be as big as we expect. Thus a direct copy