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=-6.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=ham 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 283D5C10F14 for ; Thu, 3 Oct 2019 16:35:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id F32CA20830 for ; Thu, 3 Oct 2019 16:35:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570120538; bh=GXTzmmEwG7pUp4GxtgmM28+KU55hpLHTYgwOKghYUXg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=H9VFmLvwzSZRzUYhWCw8hKjA/6qbRypsWjg9UI4iJnvHXP4LUwiUonCCh85QN7elQ BdN+3wF/r0vQYRIWctZvUYi8/PhcKZt3DwdmNjN6Sf1afv5qglPUE51bjiktVBdLI2 DO+MvHNKwKyhvHeY7Oh2PMB/gHNmEknjjtzEIHis= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390405AbfJCQfh (ORCPT ); Thu, 3 Oct 2019 12:35:37 -0400 Received: from mail.kernel.org ([198.145.29.99]:44528 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404264AbfJCQfg (ORCPT ); Thu, 3 Oct 2019 12:35:36 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id AB9032086A; Thu, 3 Oct 2019 16:35:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570120535; bh=GXTzmmEwG7pUp4GxtgmM28+KU55hpLHTYgwOKghYUXg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=dVh8NWfov0CymVIX4EC3pmSdL+o5N3jKJtD3Ay7eCJx4bf2AQeT+tFRDRISVqNejG tlKIAN9pqllIwie9PIhR2AWsl9VkSFi0E8eQ1a+S2LqojTDPiIIsa9u6Rrl9T9uTue +0xQESQWn5VImGXjeLztdOG+DPe/34gTiG47nw6k= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Thadeu Lima de Souza Cascardo , Thomas Gleixner Subject: [PATCH 5.2 259/313] alarmtimer: Use EOPNOTSUPP instead of ENOTSUPP Date: Thu, 3 Oct 2019 17:53:57 +0200 Message-Id: <20191003154558.542692115@linuxfoundation.org> X-Mailer: git-send-email 2.23.0 In-Reply-To: <20191003154533.590915454@linuxfoundation.org> References: <20191003154533.590915454@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org From: Thadeu Lima de Souza Cascardo commit f18ddc13af981ce3c7b7f26925f099e7c6929aba upstream. ENOTSUPP is not supposed to be returned to userspace. This was found on an OpenPower machine, where the RTC does not support set_alarm. On that system, a clock_nanosleep(CLOCK_REALTIME_ALARM, ...) results in "524 Unknown error 524" Replace it with EOPNOTSUPP which results in the expected "95 Operation not supported" error. Fixes: 1c6b39ad3f01 (alarmtimers: Return -ENOTSUPP if no RTC device is present) Signed-off-by: Thadeu Lima de Souza Cascardo Signed-off-by: Thomas Gleixner Cc: stable@vger.kernel.org Link: https://lkml.kernel.org/r/20190903171802.28314-1-cascardo@canonical.com Signed-off-by: Greg Kroah-Hartman --- kernel/time/alarmtimer.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) --- a/kernel/time/alarmtimer.c +++ b/kernel/time/alarmtimer.c @@ -673,7 +673,7 @@ static int alarm_timer_create(struct k_i enum alarmtimer_type type; if (!alarmtimer_get_rtcdev()) - return -ENOTSUPP; + return -EOPNOTSUPP; if (!capable(CAP_WAKE_ALARM)) return -EPERM; @@ -791,7 +791,7 @@ static int alarm_timer_nsleep(const cloc int ret = 0; if (!alarmtimer_get_rtcdev()) - return -ENOTSUPP; + return -EOPNOTSUPP; if (flags & ~TIMER_ABSTIME) return -EINVAL;