From: Matti Vaittinen <matti.vaittinen@nokia.com>
To: "David S. Miller" <davem@davemloft.net>,
Johannes Berg <johannes.berg@intel.com>,
Jiri Benc <jbenc@redhat.com>,
Matti Vaittinen <matti.vaittinen@nokia.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Sverdlin Alexander <alexander.sverdlin@nokia.com>,
Pennanen Teppo Olavi <teppo.o.pennanen@nokia.com>
Subject: [PATCH v2 1/1] net: netlink: Fix multicast group storage allocation for families with more than one groups
Date: Wed, 13 Jan 2016 09:54:12 +0200 [thread overview]
Message-ID: <20160113075400.GA12580@fi-ourus-dhcp00977.emea.nsn-net.net> (raw)
Hello again,
Second version, Fixed the 'off by one' bug spotted by David.
Br.
Matti Vaittinen
Multicast groups are stored in global buffer. Check for needed buffer size
incorrectly compares buffer size to first id for family. This means that
for families with more than one mcast id one may allocate too small buffer
and end up writing rest of the groups to some unallocated memory. Fix the
buffer size check to compare allocated space to last mcast id for the
family.
Tested on ARM using kernel 3.14
Signed-off-by: Matti Vaittinen <matti.vaittinen@nokia.com>
---
net/netlink/genetlink.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/netlink/genetlink.c b/net/netlink/genetlink.c
index bc0e504..5e113ba 100644
--- a/net/netlink/genetlink.c
+++ b/net/netlink/genetlink.c
@@ -185,7 +185,7 @@ static int genl_allocate_reserve_groups(int n_groups, int *first_id)
}
}
- if (id >= mc_groups_longs * BITS_PER_LONG) {
+ if (id + n_groups > mc_groups_longs * BITS_PER_LONG) {
unsigned long new_longs = mc_groups_longs +
BITS_TO_LONGS(n_groups);
size_t nlen = new_longs * sizeof(unsigned long);
--
2.1.0
next reply other threads:[~2016-01-13 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 7:54 Matti Vaittinen [this message]
2016-01-13 15:27 ` [PATCH v2 1/1] net: netlink: Fix multicast group storage allocation for families with more than one groups 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=20160113075400.GA12580@fi-ourus-dhcp00977.emea.nsn-net.net \
--to=matti.vaittinen@nokia.com \
--cc=alexander.sverdlin@nokia.com \
--cc=davem@davemloft.net \
--cc=jbenc@redhat.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=teppo.o.pennanen@nokia.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).