netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Julian Anastasov <ja@ssi.bg>
Cc: Hannes Eder <heder@google.com>,
	Wensong Zhang <wensong@linux-vs.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Simon Horman <horms@verge.net.au>
Subject: Re: [PATCH] ipvs: Add boundary check on ioctl arguments
Date: Thu, 1 Oct 2009 09:22:20 +0200	[thread overview]
Message-ID: <20091001092220.2ea81cb2@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0909302231360.2853@u.domain.uli>

On Wed, 30 Sep 2009 22:41:05 +0300 (EEST)
Julian Anastasov <ja@ssi.bg> wrote:

> 
> 	Hello,
> 
> On Wed, 30 Sep 2009, Arjan van de Ven wrote:
> 
> > fair enough; updated patch below



> Later len can be checked
> additionally and surely can exceed 128 (include/linux/ip_vs.h has
> all user structures). 

the on-stack structure currently is 128 bytes though...

> Can you show the exact cmd and len
> used, may be there is error in some command or may be the
> provided user structure is wrong?

this comes from code inspection using gcc features; this
is one of the (few) cases in the kernel where gcc cannot prove
that the copy_from_user() length for the copy-to-stack is sufficiently
bounds checked. I'm trying to make sure all these cases have
complete enough checks, both for the obvious security reasons but
also to be able to then make gcc emit a warning to prevent future
issues from popping up.



-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2009-10-01 21:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 11:11 [PATCH] ipvs: Add boundary check on ioctl arguments Arjan van de Ven
2009-09-30 13:38 ` Hannes Eder
2009-09-30 15:18   ` Arjan van de Ven
2009-09-30 15:33     ` Hannes Eder
2009-09-30 19:41     ` Julian Anastasov
2009-10-01  7:22       ` Arjan van de Ven [this message]
2009-10-02  8:35     ` Julian Anastasov
2009-12-15  6:17 ` Arjan van de Ven
2009-12-15  6:32   ` Simon Horman
2009-12-24  4:16     ` Simon Horman
  -- strict thread matches above, loose matches on Subject: below --
2009-12-29  1:58 Simon Horman
2010-01-04 13:59 ` Patrick McHardy
2010-01-04 15:34   ` Arjan van de Ven
2010-01-04 15:39     ` Patrick McHardy
2010-01-04 23:25       ` Simon Horman

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=20091001092220.2ea81cb2@infradead.org \
    --to=arjan@infradead.org \
    --cc=heder@google.com \
    --cc=horms@verge.net.au \
    --cc=ja@ssi.bg \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=wensong@linux-vs.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).