From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752472AbbE0WUp (ORCPT ); Wed, 27 May 2015 18:20:45 -0400 Received: from mail-lb0-f177.google.com ([209.85.217.177]:34533 "EHLO mail-lb0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751517AbbE0WUn (ORCPT ); Wed, 27 May 2015 18:20:43 -0400 Date: Thu, 28 May 2015 01:20:40 +0300 From: Cyrill Gorcunov To: Alexey Dobriyan Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, jarod@redhat.com, jstancek@redhat.com Subject: Re: [PATCH 1/2] prctl: more prctl(PR_SET_MM_*) checks Message-ID: <20150527222040.GH17625@uranus.sw.swsoft.com> References: <20150527214757.GA12863@p183.telecom.by> <20150527220229.GF17625@uranus.sw.swsoft.com> <20150527221214.GA27996@p183.telecom.by> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150527221214.GA27996@p183.telecom.by> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 28, 2015 at 01:12:14AM +0300, Alexey Dobriyan wrote: > On Thu, May 28, 2015 at 01:02:29AM +0300, Cyrill Gorcunov wrote: > > On Thu, May 28, 2015 at 12:47:57AM +0300, Alexey Dobriyan wrote: > > > Individual prctl(PR_SET_MM_*) calls do some checking to maintain > > > consistent view of mm->arg_start et al fields, but not enough. > > > In particular PR_SET_MM_ARG_START/PR_SET_MM_ARG_END/PR_SET_MM_ENV_START/PR_SET_MM_ENV_END > > > only check that address lies in existent VMA, but doesn't check that > > > start address is lower that end address _at all_. > > > > > > Consolidate all consistency checks, so there will be no difference in > > > the future between PR_SET_MM_MAP and individual PR_SET_MM_* calls. > > > > > > The program below makes both ARGV and ENVP areas reverted, > > > makes /proc/$PID/cmdline show garbage (doesn't oops by luck). > > > > Why should it oops? > > Anything can happen if you constantly write code like this > > unsigned long len = mm->arg_end - mm->arg_start; > > and expect result to be positive. It won't 'cause proc code will limit it (this where 'luck' comes from :). Anyway, switching to validate() helper will make code more robust, so thank you!