[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADxym3b-cNL5KpyKFJeiW1Su7rCok5rXqMY+qg2R6MLW8O4qXg@mail.gmail.com>
Date: Sat, 17 Aug 2024 19:36:43 +0800
From: Menglong Dong <menglong8.dong@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: pshelar@....org, davem@...emloft.net, edumazet@...gle.com,
pabeni@...hat.com, amorenoz@...hat.com, netdev@...r.kernel.org,
dev@...nvswitch.org, linux-kernel@...r.kernel.org,
Menglong Dong <dongml2@...natelecom.cn>
Subject: Re: [PATCH net-next] net: ovs: fix ovs_drop_reasons error
On Sat, Aug 17, 2024 at 9:01 AM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Thu, 15 Aug 2024 20:22:45 +0800 Menglong Dong wrote:
> > I'm sure if I understand it correctly, but it seems that there is
> > something wrong with ovs_drop_reasons.
> >
> > ovs_drop_reasons[0] is "OVS_DROP_LAST_ACTION", but
> > OVS_DROP_LAST_ACTION == __OVS_DROP_REASON + 1, which means that
> > ovs_drop_reasons[1] should be "OVS_DROP_LAST_ACTION".
> >
> > Fix this by initializing ovs_drop_reasons with index.
> >
> > Fixes: 9d802da40b7c ("net: openvswitch: add last-action drop reason")
> > Signed-off-by: Menglong Dong <dongml2@...natelecom.cn>
>
> Could you include output? Presumably from drop monitor?
> I think it should go to net rather than net-next.
I have not tested it yet. I just copy all the code for drop reason
subsystem from openvswitch to vxlan, and this happens in
the vxlan code.
I'm on vacation right now, and I'll test it out next Monday.
Thanks!
Menglong Dong
> --
> pw-bot: cr
Powered by blists - more mailing lists