On Tue, Nov 22, 2016 at 3:12 AM, Jan Beulich wrote:
> >>> On 14.11.16 at 11:34, wrote:
> > They need to be range checked against the current table limit in any
> > event.
> >
> > Reported-by: Huawei PSIRT
> >
> > Move the code to where it belongs, eliminating a number of duplicate
> > definitio
On Tue, Nov 22, 2016 at 09:17:43AM -0700, Jan Beulich wrote:
> >>> On 22.11.16 at 17:13, wrote:
> > On Tue, Nov 22, 2016 at 3:12 AM, Jan Beulich wrote:
> >
> >> >>> On 14.11.16 at 11:34, wrote:
> >> > They need to be range checked against the current table limit in any
> >> > event.
> >> >
> >>
>>> On 22.11.16 at 17:13, wrote:
> On Tue, Nov 22, 2016 at 3:12 AM, Jan Beulich wrote:
>
>> >>> On 14.11.16 at 11:34, wrote:
>> > They need to be range checked against the current table limit in any
>> > event.
>> >
>> > Reported-by: Huawei PSIRT
>> >
>> > Move the code to where it belongs, el
>>> On 14.11.16 at 11:34, wrote:
> They need to be range checked against the current table limit in any
> event.
>
> Reported-by: Huawei PSIRT
>
> Move the code to where it belongs, eliminating a number of duplicate
> definitions. Add locking. Produce proper error codes, and consume them
> inst