Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933274AbaBDXtG (ORCPT ); Tue, 4 Feb 2014 18:49:06 -0500 Received: from v094114.home.net.pl ([79.96.170.134]:65269 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1754718AbaBDXtA (ORCPT ); Tue, 4 Feb 2014 18:49:00 -0500 From: "Rafael J. Wysocki" To: Sebastian Capella Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-pm@vger.kernel.org, linaro-kernel@lists.linaro.org, patches@linaro.org, Pavel Machek , Len Brown Subject: Re: [PATCH v7 2/3] trivial: PM / Hibernate: clean up checkpatch in hibernate.c Date: Wed, 05 Feb 2014 01:03:29 +0100 Message-ID: <1593382.PUxxx0NMeh@vostro.rjw.lan> User-Agent: KMail/4.11.4 (Linux/3.13.0+; KDE/4.11.4; x86_64; ; ) In-Reply-To: <20140204232222.31169.83206@capellas-linux> References: <1391546631-7715-1-git-send-email-sebastian.capella@linaro.org> <20140204223733.30015.23993@capellas-linux> <20140204232222.31169.83206@capellas-linux> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday, February 04, 2014 03:22:22 PM Sebastian Capella wrote: > Quoting Sebastian Capella (2014-02-04 14:37:33) > > Quoting Rafael J. Wysocki (2014-02-04 13:36:29) > > > > static int __init resumedelay_setup(char *str) > > > > { > > > > - resume_delay = simple_strtoul(str, NULL, 0); > > > > + int ret = kstrtoint(str, 0, &resume_delay); > > > > + /* mask must_check warn; on failure, leaves resume_delay unchanged */ > > > > + (void)ret; > > One unintended consequence of this change is that it'll now accept a > negative integer parameter. Well, what about using kstrtouint(), then? > I'll rework this to have the same behavior as before. > > BTW, one question, is the __must_check really needed on kstrtoint? > Wouldn't it be acceptable to rely on kstrtoint to not update resume_delay > if it's unable to parse an integer out of the string? Couldn't that be > a sufficient effect without requiring checking the return? Well, kstrtoint() is used in some security-sensitive places AFAICS, so it really is better to check its return value in general. The __must_check reminds people about that. Thanks! -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- 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/