From: Cyrill Gorcunov <gorcunov@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] net,socket: introduce build_sockaddr_check helper to catch overflow at build time
Date: Thu, 22 Oct 2009 17:55:57 +0400 [thread overview]
Message-ID: <20091022135557.GA5162@lenovo> (raw)
In-Reply-To: <20091022.044914.36401063.davem@davemloft.net>
[David Miller - Thu, Oct 22, 2009 at 04:49:14AM -0700]
| From: Cyrill Gorcunov <gorcunov@gmail.com>
| Date: Wed, 21 Oct 2009 21:07:32 +0400
|
| > 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>
|
| Nice idea, and I wonder if we can automate it even further.
| Perhaps some tag that gets put on the socket address type
| definition or similar?
|
Thanks for review David! Not sure if I understand you right.
Initially I was trying to bring as minimum changes as possible.
Also I was shuffle in mind the following possibilities:
1) Since at least one .getname handler use memcpy, we could
introduce some helper which check size (at build time) and
then do memcpy (not optimal perhaps).
2) All handlers set *len to some size explicitly so we may
introduce set_sockaddr_size() helper like
#define set_sockaddr_size(ptr, size) \
do { \
build_sockaddr_check(size); \
*ptr = size; \
} while (0)
Or you meant something completely different?
-- Cyrill
next prev parent reply other threads:[~2009-10-22 13:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 17:07 [RFC] net,socket: introduce build_sockaddr_check helper to catch overflow at build time Cyrill Gorcunov
2009-10-22 11:49 ` David Miller
2009-10-22 13:55 ` Cyrill Gorcunov [this message]
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=20091022135557.GA5162@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).