From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754829AbaI2UFO (ORCPT ); Mon, 29 Sep 2014 16:05:14 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52641 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750968AbaI2UFM (ORCPT ); Mon, 29 Sep 2014 16:05:12 -0400 Message-ID: <1412021098.14757.6.camel@localhost> Subject: Re: [PATCH] tun: make sure interface usage can not overflow From: Hannes Frederic Sowa To: Kees Cook Cc: David Laight , "linux-kernel@vger.kernel.org" , "David S. Miller" , Jason Wang , Zhi Yong Wu , "Michael S. Tsirkin" , Tom Herbert , Masatake YAMATO , Xi Wang , stephen hemminger , "netdev@vger.kernel.org" Date: Mon, 29 Sep 2014 22:04:58 +0200 In-Reply-To: References: <20140928232753.GA31180@www.outflux.net> <063D6719AE5E284EB5DD2968C1650D6D1749FC70@AcuExch.aculab.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mo, 2014-09-29 at 12:41 -0700, Kees Cook wrote: > On Mon, Sep 29, 2014 at 4:04 AM, David Laight wrote: > > From: Kees Cook > >> This makes the size argument a const, since it is always populated by > >> the caller. > > > > There is almost no point making parameters 'const. > > ('const foo *' makes sense). > > > >> Additionally double-checks to make sure the copy_from_user > >> can never overflow, keeping CONFIG_DEBUG_STRICT_USER_COPY_CHECKS happy: > >> > >> In function 'copy_from_user', > >> inlined from '__tun_chr_ioctl' at drivers/net/tun.c:1871:7: > >> ... copy_from_user() buffer size is not provably correct > > > > If 'ifreq_len' could be too big then you want to error the ioctl, not panic. > > If it can't be too big you don't need the check. > > The ifreq_len comes from the callers, and is the output of "sizeof" > which is const. Changing the function parameter to "const" means any > changes made in the future where the incoming value isn't const, the > compiler will throw a warning. Hmmm, I think you want something like BUILD_BUG_ON(! __builtin_constant_p(var)). const in function argument only ensures that the value cannot be modified in the function. Bye, Hannes