From: David Miller <davem@davemloft.net>
To: lucien.xin@gmail.com
Cc: netdev@vger.kernel.org, simon.horman@netronome.com,
jbenc@redhat.com, tgraf@suug.ch, u9012063@gmail.com
Subject: Re: [PATCH net-next 0/5] lwtunnel: add ip and ip6 options setting and dumping
Date: Thu, 07 Nov 2019 10:34:21 -0800 (PST) [thread overview]
Message-ID: <20191107.103421.97006669944869516.davem@davemloft.net> (raw)
In-Reply-To: <CADvbK_ePx7F62BR43UAFF5dmwHKJdkU6Tth06t5iirsH9_XgLg@mail.gmail.com>
From: Xin Long <lucien.xin@gmail.com>
Date: Thu, 7 Nov 2019 18:50:15 +0800
> Now think about it again, nla_parse_nested() should always be used on
> new options, should I post a fix for it? since no code to access this
> from userspace yet.
If that is true, yes you should.
prev parent reply other threads:[~2019-11-07 18:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 9:01 [PATCH net-next 0/5] lwtunnel: add ip and ip6 options setting and dumping Xin Long
2019-11-06 9:01 ` [PATCH net-next 1/5] lwtunnel: add options process for arp request Xin Long
2019-11-06 9:01 ` [PATCH net-next 2/5] lwtunnel: add options process for cmp_encap Xin Long
2019-11-06 9:01 ` [PATCH net-next 3/5] lwtunnel: add options setting and dumping for geneve Xin Long
2019-11-06 9:01 ` [PATCH net-next 4/5] lwtunnel: add options setting and dumping for vxlan Xin Long
2019-11-06 9:01 ` [PATCH net-next 5/5] lwtunnel: add options setting and dumping for erspan Xin Long
2019-11-06 9:03 ` [PATCH net-next 0/5] lwtunnel: add ip and ip6 options setting and dumping Xin Long
2019-11-07 5:14 ` David Miller
2019-11-07 10:50 ` Xin Long
2019-11-07 16:18 ` David Ahern
2019-11-08 14:08 ` Xin Long
2019-11-08 15:29 ` David Ahern
2019-11-07 18:34 ` David Miller [this message]
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=20191107.103421.97006669944869516.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jbenc@redhat.com \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@netronome.com \
--cc=tgraf@suug.ch \
--cc=u9012063@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).