On Fri, Sep 14, 2018 at 3:46 AM Vlad Buslov wrote:
>
>
> On Thu 13 Sep 2018 at 17:13, Cong Wang wrote:
> > On Wed, Sep 12, 2018 at 1:51 AM Vlad Buslov wrote:
> >>
> >>
> >> On Fri 07 Sep 2018 at 19:12, Cong Wang wrote:
> >> > On Fri, Sep 7, 2018 at 6:52 AM Vlad Buslov wrote:
> >> >>
> >> >> Ac
On Thu 13 Sep 2018 at 17:13, Cong Wang wrote:
> On Wed, Sep 12, 2018 at 1:51 AM Vlad Buslov wrote:
>>
>>
>> On Fri 07 Sep 2018 at 19:12, Cong Wang wrote:
>> > On Fri, Sep 7, 2018 at 6:52 AM Vlad Buslov wrote:
>> >>
>> >> Action API was changed to work with actions and action_idr in concurrenc
On Wed, Sep 12, 2018 at 1:51 AM Vlad Buslov wrote:
>
>
> On Fri 07 Sep 2018 at 19:12, Cong Wang wrote:
> > On Fri, Sep 7, 2018 at 6:52 AM Vlad Buslov wrote:
> >>
> >> Action API was changed to work with actions and action_idr in concurrency
> >> safe manner, however tcf_del_walker() still uses a
On Fri 07 Sep 2018 at 19:12, Cong Wang wrote:
> On Fri, Sep 7, 2018 at 6:52 AM Vlad Buslov wrote:
>>
>> Action API was changed to work with actions and action_idr in concurrency
>> safe manner, however tcf_del_walker() still uses actions without taking a
>> reference or idrinfo->lock first, and
On Fri, Sep 7, 2018 at 6:52 AM Vlad Buslov wrote:
>
> Action API was changed to work with actions and action_idr in concurrency
> safe manner, however tcf_del_walker() still uses actions without taking a
> reference or idrinfo->lock first, and deletes them directly, disregarding
> possible concurr
Action API was changed to work with actions and action_idr in concurrency
safe manner, however tcf_del_walker() still uses actions without taking a
reference or idrinfo->lock first, and deletes them directly, disregarding
possible concurrent delete.
Add tc_action_wq workqueue to action API. Implem
