Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp594494pxf; Thu, 25 Mar 2021 09:47:55 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw1DnS99gMfwTI9grWrD/ozDJeY1Kpp+maO15I1kWkzKPe0QwxF7jI8PC0XLHj8WauxMEZv X-Received: by 2002:a17:907:3d8d:: with SMTP id he13mr10647021ejc.530.1616690875235; Thu, 25 Mar 2021 09:47:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616690875; cv=none; d=google.com; s=arc-20160816; b=VjQSfT5xKTouXsdsxHtCrcPvqC+d8qXoHInDbFePvgbdObz9Xr6CECs2wL//DmlAOT BsnzD0ylOwCFLOpjZAie9zs4BOh5CrOUdrBaRuu6ed2ah2nnK3BmBaojjfgVEJ+Kq3bu aNXpFqzu/6LL2M2TiVP4Yq2GMJMaMIvc9qRSVn3ebPe+9twEwNp7ANRuaYxOzZTt71Us q2wzq05q4i5jRzCrl+Em5dWllI+JidhDB1cgQqDyVxyBjVKY7QY1EDYlmzPQ34pvMe49 u+hn4ua/KgMMsz1xNivuzokchPQ953sBukwM9TkKBKWl6e591donVRusXzBWoQ4z7QKQ BuLQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=VXkz74om/p18FTc/ggtD/waEhXQyGXNW+IbQIQcMvEg=; b=UsjJGxOGW1BOddYTQuvIK5LeglzuFZmvrqgaOAGQpEdU6reRZlz/5XLp7SzG1J3RB8 NLQXtjyHWof6BQ9z6K1xPUffHHjzSoihYFYZVkIsy5KeSoNvc9GkVg2iiZ5SSYt1iD5y XsCSTQAAbEyWS+yaa1rPpf5soU7HnJad3qobR8YoQpaAMWPlu9B1c7sjJuyP9Ki20zDK khioB90JSNm/K1mj0nSHjAVWkMStwGN/B/E9CvwTeY3uGcYKyLDWm/vO5x7LdrTVD94I Dfnjq5m60pZdSRf+RpQa16Gsl2sXKEW0fJEsmlccBBh04LKZSJmIUT6GvXx4VmKG/cU8 ptHQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=OtSebmLD; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o16si4552074ejb.259.2021.03.25.09.47.30; Thu, 25 Mar 2021 09:47:55 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=OtSebmLD; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229719AbhCYQnf (ORCPT + 99 others); Thu, 25 Mar 2021 12:43:35 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:54171 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229666AbhCYQnN (ORCPT ); Thu, 25 Mar 2021 12:43:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1616690592; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VXkz74om/p18FTc/ggtD/waEhXQyGXNW+IbQIQcMvEg=; b=OtSebmLD83lw6cdbxXlMxaq7e0ry1nXeBLHXaoFz0XRleHG0tAUJG4aQ7IxJ7UCbxaN6Fv aMnlg5KNhxcrqn8WWW2b6wLauRZ8EXUDHepab66HblHZc1N/6VVLH/8SKZEgpsG+7gy2pZ iDCal1J4hHh9RnNA4KBs+VOpIzKd9vM= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-144-4tvlbfi4MNGohs7vQUxjag-1; Thu, 25 Mar 2021 12:43:10 -0400 X-MC-Unique: 4tvlbfi4MNGohs7vQUxjag-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 5193C18C89DF; Thu, 25 Mar 2021 16:43:08 +0000 (UTC) Received: from [10.10.112.16] (ovpn-112-16.rdu2.redhat.com [10.10.112.16]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 3159660D07; Thu, 25 Mar 2021 16:43:07 +0000 (UTC) Subject: Re: [PATCH] livepatch: klp_send_signal should treat PF_IO_WORKER like PF_KTHREAD To: Miroslav Benes , Dong Kai Cc: jpoimboe@redhat.com, jikos@kernel.org, pmladek@suse.com, axboe@kernel.dk, live-patching@vger.kernel.org, linux-kernel@vger.kernel.org References: <20210325014836.40649-1-dongkai11@huawei.com> From: Joe Lawrence Message-ID: <01cbab2f-da8b-f289-2241-d258406a4b6c@redhat.com> Date: Thu, 25 Mar 2021 12:43:06 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 3/25/21 5:26 AM, Miroslav Benes wrote: > On Thu, 25 Mar 2021, Dong Kai wrote: > >> commit 15b2219facad ("kernel: freezer should treat PF_IO_WORKER like >> PF_KTHREAD for freezing") is to fix the freezeing issue of IO threads >> by making the freezer not send them fake signals. >> >> Here live patching consistency model call klp_send_signals to wake up >> all tasks by send fake signal to all non-kthread which only check the >> PF_KTHREAD flag, so it still send signal to io threads which may lead to >> freezeing issue of io threads. > > I suppose this could happen, but it will also affect the live patching > transition if the io threads do not react to signals. > > Are you able to reproduce it easily? I mean, is there a testcase I could > use to take a closer look? > If repro is only hypothetical at this point, perhaps we can artificially create it in selftests? And useful to verify the future change you mentioned in your other reply? -- Joe