From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Linux-Netdev <netdev@vger.kernel.org>
Cc: David Miller <davem@davemloft.net>
Subject: [RFC] net,socket: introduce build_sockaddr_check helper to catch overflow at build time
Date: Wed, 21 Oct 2009 21:07:32 +0400 [thread overview]
Message-ID: <20091021170732.GE5976@lenovo> (raw)
Hi,
while were sneaking thru sockets code I've got the idea that we may
check for __kernel_sockaddr_storage overflow at build time. At moment
this structure is big enough and I hardly believe it could be overflowed
ever (hmm?).
Anyway just an idea which could be stupid perhaps but I decided to
put it out. An idea is that before copy protocol specific data in
socket->ops->getname implementation the driver code may put
build_sockaddr_check(sizeof(some_struct));
and be sure it doesn't overflow the hosting unit.
Feel free to just ignore this RFC, was just an idea to share.
-- Cyrill
---
net,socket: introduce build_sockaddr_check helper to catch overflow at build time
proto_ops->getname implies copying protocol specific data
into storage unit (particulary to __kernel_sockaddr_storage).
So when one implements new protocol he either may keep this
in mind (or may not).
Lets introduce build_sockaddr_check helper which check if
storage unit is not overfowed. Note that the check is build
time and introduce no slowdown at execution time.
Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org>
---
include/linux/socket.h | 3 +++
1 file changed, 3 insertions(+)
Index: linux-2.6.git/include/linux/socket.h
=====================================================================
--- linux-2.6.git.orig/include/linux/socket.h
+++ linux-2.6.git/include/linux/socket.h
@@ -24,6 +24,9 @@ struct __kernel_sockaddr_storage {
#include <linux/types.h> /* pid_t */
#include <linux/compiler.h> /* __user */
+#define build_sockaddr_check(size) \
+ BUILD_BUG_ON(((size) > sizeof(struct __kernel_sockaddr_storage)))
+
#ifdef __KERNEL__
# ifdef CONFIG_PROC_FS
struct seq_file;
next reply other threads:[~2009-10-21 17:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 17:07 Cyrill Gorcunov [this message]
2009-10-22 11:49 ` [RFC] net,socket: introduce build_sockaddr_check helper to catch overflow at build time David Miller
2009-10-22 13:55 ` Cyrill Gorcunov
2009-10-23 21:43 ` Cyrill Gorcunov
2009-10-24 13:12 ` David Miller
2009-10-24 16:32 ` Cyrill Gorcunov
2009-10-29 10:00 ` David Miller
2009-10-29 14:50 ` Cyrill Gorcunov
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=20091021170732.GE5976@lenovo \
--to=gorcunov@gmail.com \
--cc=davem@davemloft.net \
--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).