From: Liping Zhang <zlpnobody@gmail.com>
To: Pravin Shelar <pshelar@ovn.org>
Cc: Liping Zhang <zlpnobody@163.com>,
Pravin Shelar <pshelar@nicira.com>,
"David S. Miller" <davem@davemloft.net>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
Neil McKee <neil.mckee@inmon.com>
Subject: Re: [PATCH net V2] openvswitch: fix skb_panic due to the incorrect actions attrlen
Date: Wed, 16 Aug 2017 09:44:56 +0800 [thread overview]
Message-ID: <CAML_gOdF=7JAqK4Y8y_9t6t-ajHupHDkFF3wTW-bX28dHXcrPw@mail.gmail.com> (raw)
In-Reply-To: <CAOrHB_CTHWMJEp_QG3EKn07sWk1QKPe8CEBx_4860u_GRKr12g@mail.gmail.com>
2017-08-16 7:35 GMT+08:00 Pravin Shelar <pshelar@ovn.org>:
[...]
>> diff --git a/net/openvswitch/actions.c b/net/openvswitch/actions.c
>> index e4610676299b..f849ef52853f 100644
>> --- a/net/openvswitch/actions.c
>> +++ b/net/openvswitch/actions.c
>> @@ -921,6 +921,7 @@ static int output_userspace(struct datapath *dp, struct sk_buff *skb,
>> /* Include actions. */
>> upcall.actions = actions;
>> upcall.actions_len = actions_len;
>> + upcall.actions_attrlen = OVS_CB(skb)->acts_origlen;
> OVS_CB acts_origlen should be accessible in upcall_msg_size (), is
> there reason to add this member to struct dp_upcall_info?
Hmm... this means we should add an extra parameter to the upcall_msg_size()
function, i.e.:
static size_t upcall_msg_size(const struct dp_upcall_info *upcall_info,
- unsigned int hdrlen)
+ unsigned int hdrlen, int actions_attrlen)
So which one do you prefer? If the latter, I can send V3.
next prev parent reply other threads:[~2017-08-16 1:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 11:29 [PATCH net V2] openvswitch: fix skb_panic due to the incorrect actions attrlen Liping Zhang
2017-08-15 23:35 ` Pravin Shelar
2017-08-16 1:44 ` Liping Zhang [this message]
2017-08-16 3:18 ` Pravin Shelar
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='CAML_gOdF=7JAqK4Y8y_9t6t-ajHupHDkFF3wTW-bX28dHXcrPw@mail.gmail.com' \
--to=zlpnobody@gmail.com \
--cc=davem@davemloft.net \
--cc=neil.mckee@inmon.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--cc=pshelar@ovn.org \
--cc=zlpnobody@163.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.