From: Stephen Hemminger <stephen@networkplumber.org>
To: Ivan Delalande <colona@arista.com>
Cc: David Miller <davem@davemloft.net>,
Eric Dumazet <eric.dumazet@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3 1/2] inet_diag: allow protocols to provide additional data
Date: Tue, 29 Aug 2017 15:34:49 -0700 [thread overview]
Message-ID: <20170829153449.5f2cfadb@xeon-e3> (raw)
In-Reply-To: <20170829222954.24863-2-colona@arista.com>
On Tue, 29 Aug 2017 15:29:53 -0700
Ivan Delalande <colona@arista.com> wrote:
> @@ -452,13 +466,14 @@ int inet_diag_dump_one_icsk(struct inet_hashinfo *hashinfo,
> struct net *net = sock_net(in_skb->sk);
> struct sk_buff *rep;
> struct sock *sk;
> + bool net_admin = netlink_net_capable(in_skb, CAP_NET_ADMIN);
Please keep declarations in Christmas tree order if possible.
int inet_sk_diag_fill(struct sock *sk, struct inet_connection_sock *icsk,
struct sk_buff *skb, const struct inet_diag_req_v2 *req,
struct user_namespace *user_ns,
u32 portid, u32 seq, u16 nlmsg_flags,
const struct nlmsghdr *unlh,
bool net_admin)
{
bool net_admin = netlink_net_capable(in_skb, CAP_NET_ADMIN);
const struct tcp_congestion_ops *ca_ops;
const struct inet_diag_handler *handler;
int ext = req->idiag_ext;
struct inet_diag_msg *r;
struct nlmsghdr *nlh;
struct nlattr *attr;
void *info = NULL;
next prev parent reply other threads:[~2017-08-29 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 22:29 [PATCH net-next v3 0/2] report TCP MD5 signing keys and addresses Ivan Delalande
2017-08-29 22:29 ` [PATCH net-next v3 1/2] inet_diag: allow protocols to provide additional data Ivan Delalande
2017-08-29 22:34 ` Stephen Hemminger [this message]
2017-08-29 22:29 ` [PATCH net-next v3 2/2] tcp_diag: report TCP MD5 signing keys and addresses Ivan Delalande
2017-08-29 23:01 ` Eric Dumazet
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=20170829153449.5f2cfadb@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=colona@arista.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.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 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.