From: Akshat Kakkar <akshat.1984@gmail.com>
To: Cong Wang <cwang@twopensource.com>
Cc: Florian Westphal <fw@strlen.de>, netdev <netdev@vger.kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>,
Cong Wang <xiyou.wangcong@gmail.com>
Subject: Re: iproute2: Behavioural Bug?
Date: Tue, 25 Aug 2015 12:48:51 +0530 [thread overview]
Message-ID: <CAA5aLPjLhLdp2QPMw-ZvNOVjsewnM3TqV4zHFfY2_HX0UOqoFg@mail.gmail.com> (raw)
In-Reply-To: <CAHA+R7OWyfupqmCk69ykN7TP+sMwUyVtFNX=Mr_Q9DCXRSx6fw@mail.gmail.com>
Well if that is the case, then just an additional information (which I
have initially mentioned though), if hashtable is 800, then behaviour
is correct i.e. deleting only a single filter but for hash tables
other than 800, the bug (if any) gets triggered.
On Tue, Aug 25, 2015 at 11:38 AM, Cong Wang <cwang@twopensource.com> wrote:
> On Mon, Aug 24, 2015 at 10:14 PM, Akshat Kakkar <akshat.1984@gmail.com> wrote:
>> Dear Florian,
>>
>> There are two filters 15:2:2 and 15:2:3 and I have deleted only
>> 15:2:3, so 15:2:2 will still be there and hence this condition
>> "destroy proto tp when all filters are gone" should not be applicable
>> over here.
>>
>
> Florian is correct, it _does_ look like this is caused by my patch,
> I guess some check in u32_destroy() isn't correct.
>
> It's late here, I will look into this tomorrow.
>
> Thanks for the report anyway!
next prev parent reply other threads:[~2015-08-25 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 8:30 iproute2: Behavioural Bug? Akshat Kakkar
2015-08-24 19:17 ` Vadim Kochan
2015-08-24 23:22 ` Florian Westphal
2015-08-25 5:14 ` Akshat Kakkar
2015-08-25 6:08 ` Cong Wang
2015-08-25 7:18 ` Akshat Kakkar [this message]
2015-08-25 21:00 ` Cong Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA5aLPjLhLdp2QPMw-ZvNOVjsewnM3TqV4zHFfY2_HX0UOqoFg@mail.gmail.com \
--to=akshat.1984@gmail.com \
--cc=cwang@twopensource.com \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).