From: "Li,Rongqing" <lirongqing@baidu.com>
To: Pravin Shelar <pshelar@ovn.org>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: 答复: [PATCH] openvswitch: change type of UPCALL_PID attribute to NLA_UNSPEC
Date: Thu, 26 Sep 2019 01:15:35 +0000 [thread overview]
Message-ID: <e3535a264e3a4dedb3ab9ab88e907b5b@baidu.com> (raw)
In-Reply-To: <CAOrHB_Drgcyxa_2yR4QyyUTkADxT=mdRwPSKOgTrefpnQq5-=g@mail.gmail.com>
> -----邮件原件-----
> 发件人: Pravin Shelar [mailto:pshelar@ovn.org]
> 发送时间: 2019年9月26日 5:03
> 收件人: Li,Rongqing <lirongqing@baidu.com>
> 抄送: Linux Kernel Network Developers <netdev@vger.kernel.org>
> 主题: Re: [PATCH] openvswitch: change type of UPCALL_PID attribute to
> NLA_UNSPEC
>
> On Tue, Sep 24, 2019 at 4:11 AM Li RongQing <lirongqing@baidu.com> wrote:
> >
> > userspace openvswitch patch "(dpif-linux: Implement the API functions
> > to allow multiple handler threads read upcall)"
> > changes its type from U32 to UNSPEC, but leave the kernel unchanged
> >
> > and after kernel 6e237d099fac "(netlink: Relax attr validation for
> > fixed length types)", this bug is exposed by the below warning
> >
> > [ 57.215841] netlink: 'ovs-vswitchd': attribute type 5 has an
> invalid length.
> >
> > Signed-off-by: Li RongQing <lirongqing@baidu.com>
>
> Acked-by: Pravin B Shelar <pshelar@ovn.org>
>
Add a fixes:
Fixes: 5cd667b0a456 ("openvswitch: Allow each vport to have an array of 'port_id's")
-LI
> Thanks,
> Pravin.
next prev parent reply other threads:[~2019-09-26 1:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 11:11 [PATCH] openvswitch: change type of UPCALL_PID attribute to NLA_UNSPEC Li RongQing
2019-09-25 21:02 ` Pravin Shelar
2019-09-26 1:15 ` Li,Rongqing [this message]
2019-09-26 7:33 ` David Miller
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=e3535a264e3a4dedb3ab9ab88e907b5b@baidu.com \
--to=lirongqing@baidu.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.org \
/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