Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758742AbbGHKyQ (ORCPT ); Wed, 8 Jul 2015 06:54:16 -0400 Received: from ozlabs.org ([103.22.144.67]:54691 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758236AbbGHKyK (ORCPT ); Wed, 8 Jul 2015 06:54:10 -0400 X-powerpc-patch-notification: thanks X-powerpc-patch-commit: 5caaf5346892d1e7f0b8b7223062644f8538483f In-Reply-To: <1436247946-16292-2-git-send-email-imunsie@au.ibm.com> To: Ian Munsie From: Michael Ellerman Cc: Matt Ochs , linuxppc-dev , mikey , linux-kernel , Ian Munsie Subject: Re: [2/2] cxl: Fail mmap if requested mapping is larger than assigned problem state area Message-Id: <20150708105409.9D407140B0E@ozlabs.org> Date: Wed, 8 Jul 2015 20:54:09 +1000 (AEST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1236 Lines: 27 On Tue, 2015-07-07 at 05:45:46 UTC, Ian Munsie wrote: > From: Ian Munsie > > This patch makes the mmap call fail outright if the requested region is > larger than the problem state area assigned to the context so the error > is reported immediately rather than waiting for an attempt to access an > address out of bounds. > > Although we never expect users to map more than the assigned problem > state area and are not aware of anyone doing this (other than for > testing), this does have the potential to break users if someone has > used a larger range regardless. I'm submitting it for consideration, but > if this change is not considered acceptable the previous patch is > sufficient to prevent access out of bounds without breaking anyone. > > Signed-off-by: Ian Munsie Applied to powerpc fixes, thanks. https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=5caaf5346892d1e7f0b8b7223062644f8538483f cheers -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/