From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 800C0C432C3 for ; Sat, 16 Nov 2019 16:29:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5D052214DE for ; Sat, 16 Nov 2019 16:29:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728184AbfKPQ3m (ORCPT ); Sat, 16 Nov 2019 11:29:42 -0500 Received: from verein.lst.de ([213.95.11.211]:49370 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727606AbfKPQ3l (ORCPT ); Sat, 16 Nov 2019 11:29:41 -0500 Received: by verein.lst.de (Postfix, from userid 2407) id CE9D568BE1; Sat, 16 Nov 2019 17:29:37 +0100 (CET) Date: Sat, 16 Nov 2019 17:29:37 +0100 From: Christoph Hellwig To: Andy Shevchenko Cc: linux-kernel@vger.kernel.org, Christoph Hellwig , Dan Williams , Arnd Bergmann , Marek Szyprowski , Robin Murphy , Jaroslav Kysela , Takashi Iwai , Pierre-Louis Bossart , Ard Biesheuvel , Alex Williamson , Cornelia Huck Subject: Re: [PATCH v1 1/5] memremap: Check for size parameter Message-ID: <20191116162937.GA23951@lst.de> References: <20191115180044.83659-1-andriy.shevchenko@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191115180044.83659-1-andriy.shevchenko@linux.intel.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 15, 2019 at 08:00:40PM +0200, Andy Shevchenko wrote: > There is no use of memremap() to be called with size = 0. > Simple return NULL pointer and allow callers to drop this check. Given that this really is an error condition, maybe a WARN_ON_ONCE would fit here?