From: Johannes Berg <johannes@sipsolutions.net>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
davem@davemloft.net, Netdev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] af_netlink: give correct bounds to dump skb for NLMSG_DONE
Date: Wed, 08 Nov 2017 07:16:33 +0100 [thread overview]
Message-ID: <1510121793.8974.1.camel@sipsolutions.net> (raw)
In-Reply-To: <20171107112914.30576-1-Jason@zx2c4.com>
On Tue, 2017-11-07 at 20:29 +0900, Jason A. Donenfeld wrote:
>
> This patch thus reserves and restores the required length for
> NLMSG_DONE during the call to the dump function.
>
That basically removes that space though, even when the dump isn't
complete... wouldn't it be better to do something like this?
diff --git a/net/netlink/af_netlink.c b/net/netlink/af_netlink.c
index f34750691c5c..fccf83598dab 100644
--- a/net/netlink/af_netlink.c
+++ b/net/netlink/af_netlink.c
@@ -2183,9 +2183,15 @@ static int netlink_dump(struct sock *sk)
skb_reserve(skb, skb_tailroom(skb) - alloc_size);
netlink_skb_set_owner_r(skb, sk);
- len = cb->dump(skb, cb);
+ /* if the dump is already done, just complete */
+ if (nlk->dump_done)
+ len = 0;
+ else
+ len = cb->dump(skb, cb);
+
+ nlk->dump_done = len == 0;
- if (len > 0) {
+ if (len > 0 || skb_tailroom(skb) < nlmsg_total_size(sizeof(len))) {
mutex_unlock(nlk->cb_mutex);
if (sk_filter(sk, skb))
@@ -2196,7 +2202,7 @@ static int netlink_dump(struct sock *sk)
}
nlh = nlmsg_put_answer(skb, cb, NLMSG_DONE, sizeof(len), NLM_F_MULTI);
- if (!nlh)
+ if (WARN_ON(!nlh))
goto errout_skb;
nl_dump_check_consistent(cb, nlh);
@@ -2273,6 +2279,7 @@ int __netlink_dump_start(struct sock *ssk, struct sk_buff *skb,
}
nlk->cb_running = true;
+ nlk->dump_done = false;
mutex_unlock(nlk->cb_mutex);
diff --git a/net/netlink/af_netlink.h b/net/netlink/af_netlink.h
index 3490f2430532..91a3652d384f 100644
--- a/net/netlink/af_netlink.h
+++ b/net/netlink/af_netlink.h
@@ -33,6 +33,7 @@ struct netlink_sock {
wait_queue_head_t wait;
bool bound;
bool cb_running;
+ bool dump_done;
struct netlink_callback cb;
struct mutex *cb_mutex;
struct mutex cb_def_mutex;
https://p.sipsolutions.net/90574c3c0116d68a.txt
(untested)
johannes
next prev parent reply other threads:[~2017-11-08 6:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 11:29 [PATCH] af_netlink: give correct bounds to dump skb for NLMSG_DONE Jason A. Donenfeld
2017-11-08 6:03 ` Jason A. Donenfeld
2017-11-08 6:16 ` Johannes Berg [this message]
2017-11-08 6:35 ` Jason A. Donenfeld
2017-11-08 7:06 ` Jason A. Donenfeld
2017-11-08 7:21 ` [PATCH v2] " Jason A. Donenfeld
2017-11-09 1:42 ` [PATCH v3] af_netlink: ensure that NLMSG_DONE never fails in dumps Jason A. Donenfeld
2017-11-09 2:02 ` Johannes Berg
2017-11-09 2:57 ` Jason A. Donenfeld
2017-11-09 4:04 ` [PATCH v4] " Jason A. Donenfeld
2017-11-11 2:26 ` Jason A. Donenfeld
2017-11-11 2:37 ` David Miller
2017-11-11 2:47 ` Jason A. Donenfeld
2017-11-11 14:09 ` David Miller
2017-11-11 14:15 ` Johannes Berg
2017-11-11 14:18 ` Johannes Berg
2017-11-11 15:18 ` Jason A. Donenfeld
2017-11-11 14:21 ` David Miller
2017-11-13 1:18 ` 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=1510121793.8974.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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 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).