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=-7.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 AC668C433E0 for ; Thu, 25 Mar 2021 20:45:27 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 724E461A43 for ; Thu, 25 Mar 2021 20:45:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230313AbhCYUoy (ORCPT ); Thu, 25 Mar 2021 16:44:54 -0400 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:40779 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230263AbhCYUoj (ORCPT ); Thu, 25 Mar 2021 16:44:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1616705078; 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: in-reply-to:in-reply-to:references:references; bh=QRNZIFWxRM57bHTCCTJ1A2JvKV0FOZM1E6K3THZHiOg=; b=K2QSliinGuCnIHmQDOKWd8xLRI4nn+v0fFHZJTclMJ0dABmnmHF5CJ8Z/ftNUfL4UUT6RE QhEyfm4iKmIkWqmIoI3FUAq4+zFBv2V6kPBAGCZy86tgvh0IZfe2uvMoH79zXdx24CU+fe euI3ASRtpLjpJ0M+tFCy5fEpaMt/psM= 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-540-xis2Tf1rPa2feoa4YPKEnQ-1; Thu, 25 Mar 2021 16:44:34 -0400 X-MC-Unique: xis2Tf1rPa2feoa4YPKEnQ-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id B265E88127C; Thu, 25 Mar 2021 20:44:33 +0000 (UTC) Received: from dhcp-27-174.brq.redhat.com (unknown [10.40.192.41]) by smtp.corp.redhat.com (Postfix) with SMTP id 10BF813470; Thu, 25 Mar 2021 20:44:31 +0000 (UTC) Received: by dhcp-27-174.brq.redhat.com (nbSMTP-1.00) for uid 1000 oleg@redhat.com; Thu, 25 Mar 2021 21:44:33 +0100 (CET) Date: Thu, 25 Mar 2021 21:44:30 +0100 From: Oleg Nesterov To: Linus Torvalds Cc: "Eric W. Biederman" , Jens Axboe , io-uring , Linux Kernel Mailing List , Stefan Metzmacher Subject: Re: [PATCH 0/2] Don't show PF_IO_WORKER in /proc//task/ Message-ID: <20210325204430.GE28349@redhat.com> References: <20210325164343.807498-1-axboe@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org On 03/25, Linus Torvalds wrote: > > The whole "signals are very special for IO threads" thing has caused > so many problems, that maybe the solution is simply to _not_ make them > special? Or may be IO threads should not abuse CLONE_THREAD? Why does create_io_thread() abuse CLONE_THREAD ? One reason (I think) is that this implies SIGKILL when the process exits/execs, anything else? Oleg.