Received: by 2002:a05:6a10:83d0:0:0:0:0 with SMTP id o16csp42009pxh; Thu, 7 Apr 2022 13:23:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyx3vSyYp4KyEx1EJc3M4GDf4TXA4DVoVjRPLvD0hJEKhqQ2H1bdcgX5t5vPL3ZTYLED7+1 X-Received: by 2002:a63:2f03:0:b0:398:b2fc:250c with SMTP id v3-20020a632f03000000b00398b2fc250cmr12477870pgv.75.1649363029247; Thu, 07 Apr 2022 13:23:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649363029; cv=none; d=google.com; s=arc-20160816; b=I17Zm3N6hDEYrB2muBnAuR8CG0FftA8CtB30SRsjwzLjXKsCwZFYbpg0FNylzNtl62 IDOtFie+fX9ucKykavfcFmObX97dFzEQaNiSHo0NYOo5ODqjXnEpiwb+YxxcHEpquTyk uldbk/6Nvka070yfsBhDoWERXyVYgNl+orcz2psZ8h0d2rF3sahuDE40aQu30cpTjaUy p3wbL3Wr4P+vp27IEHmYjbrtseTWTchv8yNf3Z+OvtDxThY9DyJIQtTB+xf8Rg7WdopJ NyYSN/cabeSv4l0fwS3UL6V6m4S5Xh63EJq96WUYj5U5k+8l6XIFnl2fH1QcU3FyZ+mp Or+Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=M+3WC6K2v2Rew5+KY4Zz7SR5Z7lL3sysPR2qoBAMEGg=; b=CKP/SqlmIQ6LGm2rr8dQFm5K0MA5WiqBIS+h/+K+zQmOCYzj5AdOxG0RMQQrj0GKru 8eIlF/oZhGPkp83U3nlu5fzq0767S85s9+YpTRO7S/byNVN2q2Wz2qFRx//7/YsEcaTD 7esk+FdSt8r/DapCsZNvxQZcFiYGlFG85NtfsMIhLOtKwgQubohc1n7RmXoDpbaDolKL 52/wkKjjBiQjXEA4vObU0W9l6vtnoTK0/f/U5fMsUYFVoJ2OP8GY5rp220bb0fJNkgyN ThEsVihKQv/qmJfeUp5p+5R7G8goXzcazTBJy3TQSuswdiJaKe4bx/2FSAsMzg0a4Hwb XXOg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=dzBjnduR; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id lx9-20020a17090b4b0900b001c7e8ae7620si2896956pjb.157.2022.04.07.13.23.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 07 Apr 2022 13:23:49 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=dzBjnduR; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 579B6360CED; Thu, 7 Apr 2022 12:42:36 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244580AbiDGK4K (ORCPT + 99 others); Thu, 7 Apr 2022 06:56:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55298 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244568AbiDGK4H (ORCPT ); Thu, 7 Apr 2022 06:56:07 -0400 Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 541CEA199; Thu, 7 Apr 2022 03:54:08 -0700 (PDT) Received: by mail-pg1-x533.google.com with SMTP id 32so2514149pgl.4; Thu, 07 Apr 2022 03:54:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=M+3WC6K2v2Rew5+KY4Zz7SR5Z7lL3sysPR2qoBAMEGg=; b=dzBjnduRmPzY2Trf1omhPW2ulIytv7bkAMJp1DfmstQ+eE+XlzZ6NiIPfM1ARC/87l Y7+fI784U5iGH0UuuiOArn89Hs6SUb3Wo1TtBHA7Um3NvBKhebIY8wrwWrXanBDzjFH7 mlbTMk88/fzd6RFcafPuepnlZp+EZh+DUiBjti5JdNnEJEUXSjc/QdClesam25s0qXKy L3T9ujxtXRxD8+50NlSfhAzRr+jPO6pS01TNlwBlm5pb9ckRjB/isfv4r3sQAZ4bp7ZB X6KFhK6dN7gzJMFb9aN2dMEwyqE+d+tjjBFyFjatL5D+FVCTyHkT3LJeH89jkdDiXEKB YIKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=M+3WC6K2v2Rew5+KY4Zz7SR5Z7lL3sysPR2qoBAMEGg=; b=xUG2/YM9kJmVD/4Qca46yIkKSkZ9HplxXiIAXuuICnl/QqFAgIi+gdg8+vssPkZAOv o0fvmGs8ph+on4gm7DJ4qxEweipvm1MPsOQjS45BnCPegwW2wZCSYxaZ891nTKwWaJvE ntZ60tGMuhRcP6pp7Zk67D5Syny/2RU8bjYn/2MWa2S/+n5ecsHHKB0F/E/DsMVugJUF jfqhyuVOZHBwe1UYCSlYshxrLiCqE/sq+VaLEFXKgrZCrOQ5c0z6NS+sDfplq2vpD76a la6VqVdlyqJ0vArVjw+3JJadY79Ti+HQVHcq5ZH9KfGvbV0A7gfgeopQHHQxBeWLiOhH OWmg== X-Gm-Message-State: AOAM5335641Ozp9iY2d5USX9VMF/NpTCu6ZHXyPoBH1bay78JfiLg4GC DD+VYv8KwEn/yhPsYzUVCY6ZSzHYmignbg37/ByU84QuhwKrOHw= X-Received: by 2002:a05:6a00:1897:b0:505:6e58:4a2c with SMTP id x23-20020a056a00189700b005056e584a2cmr895665pfh.2.1649328847784; Thu, 07 Apr 2022 03:54:07 -0700 (PDT) MIME-Version: 1.0 References: <20220407101312.13331-1-W_Armin@gmx.de> In-Reply-To: <20220407101312.13331-1-W_Armin@gmx.de> From: Zheyu Ma Date: Thu, 7 Apr 2022 18:53:56 +0800 Message-ID: Subject: Re: [PATCH] hwmon: (adt7470) Fix warning on module removal To: Armin Wolf Cc: jdelvare@suse.com, linux@roeck-us.net, linux-hwmon@vger.kernel.org, Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RDNS_NONE, SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 7, 2022 at 6:13 PM Armin Wolf wrote: > > When removing the adt7470 module, a warning might be printed: > > do not call blocking ops when !TASK_RUNNING; state=1 > set at [] adt7470_update_thread+0x7b/0x130 [adt7470] > > This happens because adt7470_update_thread() can leave the kthread in > TASK_INTERRUPTIBLE state when the kthread is being stopped before > the call of set_current_state(). Since kthread_exit() might sleep in > exit_signals(), the warning is printed. > Fix that by using schedule_timeout_interruptible() and removing > the call of set_current_state(). > This causes TASK_INTERRUPTIBLE to be set after kthread_should_stop() > which might cause the kthread to exit. > > Compile-tested only. > > Reported-by: Zheyu Ma > Fixes: 93cacfd41f82 (hwmon: (adt7470) Allow faster removal) > Signed-off-by: Armin Wolf > --- > drivers/hwmon/adt7470.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/hwmon/adt7470.c b/drivers/hwmon/adt7470.c > index fb6d14d213a1..c67cd037a93f 100644 > --- a/drivers/hwmon/adt7470.c > +++ b/drivers/hwmon/adt7470.c > @@ -19,6 +19,7 @@ > #include > #include > #include > +#include > #include > #include > > @@ -294,11 +295,10 @@ static int adt7470_update_thread(void *p) > adt7470_read_temperatures(data); > mutex_unlock(&data->lock); > > - set_current_state(TASK_INTERRUPTIBLE); > if (kthread_should_stop()) > break; > > - schedule_timeout(msecs_to_jiffies(data->auto_update_interval)); > + schedule_timeout_interruptible(msecs_to_jiffies(data->auto_update_interval)); > } > > return 0; > -- > 2.30.2 > Tested-by: Zheyu Ma Thanks, Zheyu Ma