On Thu, Dec 11, 2014 at 03:40:47PM -0800, Joe Stringer wrote:
> On 11 December 2014 at 15:09, Ben Pfaff wrote:
> > On Thu, Dec 11, 2014 at 02:48:46PM -0800, Joe Stringer wrote:
> >> On 11 December 2014 at 14:05, Ben Pfaff wrote:
> >> > On Wed, Dec 03, 2014 at 02:24:46PM -0800, Joe Stringer wrote:
On Thu, Dec 11, 2014 at 02:48:46PM -0800, Joe Stringer wrote:
> On 11 December 2014 at 14:05, Ben Pfaff wrote:
> > On Wed, Dec 03, 2014 at 02:24:46PM -0800, Joe Stringer wrote:
> >> The UFID parameter to dpif_flow_get() is optional, but the current
> >> implementation dereferences it to initialize
On 11 December 2014 at 15:09, Ben Pfaff wrote:
> On Thu, Dec 11, 2014 at 02:48:46PM -0800, Joe Stringer wrote:
>> On 11 December 2014 at 14:05, Ben Pfaff wrote:
>> > On Wed, Dec 03, 2014 at 02:24:46PM -0800, Joe Stringer wrote:
>> >> The UFID parameter to dpif_flow_get() is optional, but the curr
On 11 December 2014 at 14:05, Ben Pfaff wrote:
> On Wed, Dec 03, 2014 at 02:24:46PM -0800, Joe Stringer wrote:
>> The UFID parameter to dpif_flow_get() is optional, but the current
>> implementation dereferences it to initialize part of the output flow.
>> This field is filled in by the dpif imple
On Wed, Dec 03, 2014 at 02:24:46PM -0800, Joe Stringer wrote:
> The UFID parameter to dpif_flow_get() is optional, but the current
> implementation dereferences it to initialize part of the output flow.
> This field is filled in by the dpif implementation, so don't initialize
> it here.
>
> This c
The UFID parameter to dpif_flow_get() is optional, but the current
implementation dereferences it to initialize part of the output flow.
This field is filled in by the dpif implementation, so don't initialize
it here.
This could cause a NULL dereference if a dpif_flow_get() caller doesn't
provide
