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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS 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 7307EC43460 for ; Fri, 21 May 2021 07:12:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 4BE54613CB for ; Fri, 21 May 2021 07:12:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235555AbhEUHOB (ORCPT ); Fri, 21 May 2021 03:14:01 -0400 Received: from mx2.suse.de ([195.135.220.15]:46274 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235561AbhEUHN4 (ORCPT ); Fri, 21 May 2021 03:13:56 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1621581150; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Jp4zlznkpFx9tdWxRUV7M5qNhT0kZeoN0+qL2xikpYg=; b=tUDSC0acfymWbFBzvducaP0wBVLZV872XvCF1zTWwODsy2jEiNXR0Wct16zY9MAR/cPA5E ZnnPP/g09GFGnQKDlw9ml/F5DzOVHFiiVXUfEv6QZ17S3+DHJ5y7Hg6zoCcUedvqbLpfSS HWoQiMICrUiF5LgomVsUqQ1aIOO1Mag= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 734F1AC1A; Fri, 21 May 2021 07:12:30 +0000 (UTC) Date: Fri, 21 May 2021 09:12:30 +0200 From: Petr Mladek To: Andrew Morton Cc: Martin Liu , Nathan Chancellor , Nick Desaulniers , Tejun Heo , minchan@google.com, www@google.com, davidchao@google.com, jenhaochen@google.com, linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com Subject: Re: [PATCH] kthread: Fix kthread_mod_delayed_work vs kthread_cancel_delayed_work_sync race Message-ID: References: <20210513065458.941403-1-liumartin@google.com> <20210520144845.52755f3af700a902e07e2ee7@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210520144845.52755f3af700a902e07e2ee7@linux-foundation.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 2021-05-20 14:48:45, Andrew Morton wrote: > On Thu, 13 May 2021 14:54:57 +0800 Martin Liu wrote: > > > We encountered a system hang issue while doing the tests. The callstack > > is as following > > > > ... > > > > Fixes: 37be45d49dec2 ("kthread: allow to cancel kthread work") > > Thanks. I added a cc:stable to this and shall hold it in -mm for a > couple of weeks to get exposure and testing before sending it to Linus > for 5.13. Sounds good to me. Thanks for taking care of it. Best Regards, Petr